Some sensitive environment variables synced from Vercel were cleared

What to do

• Check whether you use Trigger.dev Deployments. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 49m it lasted.

  Anything that failed between 2026-10-06 12:21 UTC and 2026-10-06 15:10 UTC may need a replay.

• Subscribe to Trigger.dev's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=trigger-dev works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Trigger.dev 2

1. degradedOct 6, 2026, 12:21 PM UTC

   Between 12:21 and 15:09 UTC, deploying with the Vercel integration overwrote some environment variables with empty values in Trigger.dev. Projects with affected variables may see failing deploys or runs that error because of missing credentials. You are only affected if all of these are true: - Your project uses the Vercel integration with environment variable syncing enabled - The project has environment variables marked as Sensitive in Vercel - That project deployed between 12:21 and 15:09 UTC today If any of these don't apply, your project was not affected and you don't need to do anything. Only the environments that deployed in that window are affected. The cause has been fixed and no new variables are being cleared. Variables that were already cleared are still empty: redeploying will not restore them. We are working on restoring them, and we are contacting affected customers directly with the list of impacted projects and variables. If you can't wait, re-entering the values in the Trigger.dev dashboard under Environment Variables fixes the affected project right away.

   provider

2. resolvedOct 6, 2026, 3:10 PM UTC

   We stopped the issue at 15:10 UTC and no environment variables have been cleared since. A permanent fix is in progress. Variables that were cleared between 12:21 and 15:10 UTC are still empty and will not come back on redeploy. We have contacted every affected customer directly. Re-entering them in the Trigger.dev dashboard under Environment Variables fixes the affected project right away. We're still working with affected customers to restore their values, so if you need help or have questions, reach out to us at support or reply to our email.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.