Hi @crude frigate. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#GitHub Integration Commit Deployment Queued
desert nexusBOT
The knowledge sources don't contain enough specific information about why a GitHub integration deployment would get stuck in a "queued" state indefinitely. This appears to be a platform/infrastructure issue rather than a configuration problem covered in the documentation.
That said, here are a few things worth checking based on what the knowledge sources do cover:
Regarding the Vercel build hanging:
The Vercel integration uses deployment checks that gate your Vercel deployment until the Trigger.dev build completes. If the Trigger.dev build is stuck, this would indeed cause Vercel to hang. [Vercel integration]
Potential workarounds to investigate:
-
Check your concurrency/queue limits — If your environment has hit its queued task limit, new deployments may be blocked. You can view current limits in the dashboard's Limits page. [Limits]
-
Try a manual deploy to see if the issue is specific to the GitHub integration trigger:
npx trigger.dev@latest deploy -
Run with debug logs to get more information:
npx trigger.dev@latest deploy --log-level debug
Recommended next step:
Since this appears to be a platform-level issue with the GitHub integration build queue, I'd strongly recommend:
- Joining the Trigger.dev Discord and creating a Help forum post with a link to your stuck deployment — the team can investigate the specific deployment on their end.