Provide environment information
n/a
Describe the bug
When importing environment variables from Vercel via the Vercel integration, only ~25 variables are offered for import even when the Vercel project has more configured. Expected: all (non-secret-type) variables from the Vercel project are available to import.
Cause (corrected 2026-08-21): the cap came from the team-level shared endpoint GET /v1/env, which pages at ~25 via an until millisecond-timestamp cursor and was only ever read one page deep. Fixed by paginating that fetch in #3879, plus the build-time sync in cloud#1074.
The original write-up below blamed the project endpoint GET /v10/projects/{idOrName}/env. That was wrong: it returns every record in one response and ignores limit. Verified against a project with 500 variables (all 500 returned in one response) and a team with 100 shared variables (returned across four pages, walked correctly). The leftover logger.warn("...returned paginated response - some env vars may be missing") in getVercelEnvironmentVariables fired on nothing and implied a cap that does not exist; removed separately.
Original (incorrect) cause, kept for the record: getVercelEnvironmentVariables calls client.projects.filterProjectEnvs() and only uses the first page of the response.
Reproduction repo
n/a
To reproduce
n/a
Additional information
- Create a Vercel project with 30+ environment variables (non secret-type).
- Connect the project to Trigger.dev via the Vercel integration.
- Open the env var import step/sync.
- Only the first ~25 variables are listed; the rest are silently missing. Server logs show the
filterProjectEnvs returned paginated response warning.
Provide environment information
n/a
Describe the bug
When importing environment variables from Vercel via the Vercel integration, only ~25 variables are offered for import even when the Vercel project has more configured. Expected: all (non-secret-type) variables from the Vercel project are available to import.
Cause (corrected 2026-08-21): the cap came from the team-level shared endpoint
GET /v1/env, which pages at ~25 via anuntilmillisecond-timestamp cursor and was only ever read one page deep. Fixed by paginating that fetch in #3879, plus the build-time sync in cloud#1074.The original write-up below blamed the project endpoint
GET /v10/projects/{idOrName}/env. That was wrong: it returns every record in one response and ignoreslimit. Verified against a project with 500 variables (all 500 returned in one response) and a team with 100 shared variables (returned across four pages, walked correctly). The leftoverlogger.warn("...returned paginated response - some env vars may be missing")ingetVercelEnvironmentVariablesfired on nothing and implied a cap that does not exist; removed separately.Original (incorrect) cause, kept for the record:
getVercelEnvironmentVariablescallsclient.projects.filterProjectEnvs()and only uses the first page of the response.Reproduction repo
n/a
To reproduce
n/a
Additional information
filterProjectEnvs returned paginated responsewarning.