> ## Documentation Index
> Fetch the complete documentation index at: https://docs.automate.ax/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Automate.ax automations are TypeScript programs.
> Use Bun for installation and command examples.
> Use Automate.ax for the product name and automate.ax for the package, CLI, and domain.
> Treat documented public APIs as current; do not invent transitional or deprecated names.

# Start rolling release

> Starts a staged production rollout for one deployment.

`vercel.startRollingRelease` starts a staged production rollout for one deployment.

```ts automations/start-rolling-release.automation.ts theme={null}
import { automation } from "automate.ax"
import { vercel } from "automate.ax/vercel"

export default automation("Start rolling release", () => {
  vercel.startRollingRelease({
    canaryDeploymentId: "dpl_1",
    idOrName: "prj_1",
    teamId: "team_1",
  })
})
```

## Input

* `canaryDeploymentId`: the deployment entering the staged rollout.
* `idOrName`: the Vercel project ID or name.
* `teamId`: the owning team ID when the project belongs to a team.

## Output

Returns `{ rollingRelease }`. Read `result.rollingRelease` for Vercel's current rolling-release document; it is `null` when no rolling release exists.

## Provider behavior

This action requires a Vercel access-token connection. It changes production traffic and is not replay-safe. Vercel rejects deployments that cannot start a rolling release for the selected project.