Troubleshooting
Panel says "Waiting for bridge messages"
Checklist:
- Ensure app calls
attachJourneyDevtools(machine). - Confirm extension is installed from Chrome Web Store (once approval is live).
- Reload page and reopen DevTools.
- Ensure bridge is not disabled by
enabled: falseor production default.
Extension not installable yet
If you cannot install the extension yet, Chrome Web Store approval is likely still pending.
In the meantime:
- Keep bridge integration in place.
- Validate machine transitions from your app UI.
- Return to this guide once the store listing is published.
Machine does not appear in selector
machineIdcollisions can hide intent.- Use unique ids per machine.
- Add explicit labels for quick visual confirmation.
Commands do nothing
Potential causes:
- target machine id mismatch
- machine already terminal (
complete/terminated) - no matching transition for event
What to inspect:
- log entry kind and summary
- snapshot
status - transition graph order and guards in your journey definition
commandError entries keep appearing
Typical reasons:
- async
whenthrows/rejects - async
effectthrows/rejects - custom event payload shape mismatch
Actions:
- Inspect async tab for per-step error details.
- Validate event payload JSON sent from panel.
- Run the same event from app UI and compare behavior.
Logs are too large
- Keep display unbounded for diagnostics.
- Set display limit during routine usage.
- Use
Prune to limitto reduce retained entries.
Multiple apps open in different tabs
The panel is tab-scoped.
- switch to a different browser tab -> panel stream changes
- each tab tracks its own machine cache
Production debugging not available
Default behavior disables bridge in production.
Use explicit enablement:
attachJourneyDevtools(machine, {
enabled: true
});
Prefer guardrails when enabling in production:
- query-param gating
- environment flag
- internal-only domains