Skip to content

docs: add troubleshooting entry for runs not dequeuing in dev #3955

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
matt-aitken merged 3 commits into from
Jun 15, 2026
+4 −0
Merged

docs: add troubleshooting entry for runs not dequeuing in dev #3955

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
071a6a6
docs: add troubleshooting entry for runs not dequeuing in dev
isshaddad Jun 15, 2026
bf81e19
docs: clarify dev dequeue conflict is one local instance per project
isshaddad Jun 15, 2026
8b6647e
Merge branch 'main' into docs/troubleshooting-dev-dequeue
isshaddad Jun 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,10 @@ If you see "Connection error" when running `trigger login` (or "Failed to create
2. **VPN or firewall:** Disconnect from VPN or check firewall/proxy; try `npx trigger.dev@latest login --log-level debug` for more detail.
3. **TLS / certificate store:** Node may use a different CA store than your OS (e.g. `curl` works but the CLI fails). Try `export NODE_EXTRA_CA_CERTS=/etc/ssl/cert.pem` (macOS/Linux) then login again, or reinstall Node so it gets updated certs. Behind a corporate proxy or custom CA? Set `NODE_EXTRA_CA_CERTS` to that CA file.

### Runs never dequeue in dev

If runs sit in the queue and never start while running `trigger.dev dev`, check whether you have more than one local instance running against the same project. Each project has a single dev environment, and only one `trigger.dev dev` instance can consume from it at a time, so a second instance causes runs to be split between them and some appear stuck. Keep a single `trigger.dev dev` running per project. [Upvote isolated dev sessions](https://triggerdev.featurebase.app/p/isolated-dev-sessions-for-multiple-local-trigger-dev-instances) if you need to run multiple local instances.

## Deployment

Running the [trigger.dev deploy] command builds and deploys your code. Sometimes there can be issues building your code.
Expand Down
Loading