Skip to content

Commit b74e01e

Browse files
committed
docs: clarify Vercel env var sync requires a new deployment
1 parent 6e6deb4 commit b74e01e

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

docs/vercel-integration.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -104,6 +104,12 @@ The following variables are excluded from the Vercel → Trigger.dev sync:
104104

105105
You can control sync behavior per-variable from your project's Vercel settings. Deselecting a variable prevents its value from being updated during future syncs.
106106

107+
<Note>
108+
Environment variables are pulled from Vercel before each build. To sync updated values into
109+
Trigger.dev, trigger a new Vercel deployment — either by pushing a commit to your connected branch
110+
or by redeploying from the Vercel dashboard.
111+
</Note>
112+
107113
<Warning>
108114
If you are experiencing incorrectly populated environment variables, check that you are not using
109115
the `syncVercelEnvVars` build extension in your `trigger.config.ts`. This extension is deprecated

0 commit comments

Comments
 (0)