Troubleshooting
Find the difference between an invalid graph, missing evidence and a failed action.
Markdown versionThe graph cannot start
- Save your latest edit and read the current validation issues.
- Check for exactly one Start and an active signal source.
- Reconnect Open trade → Time exit → Close trade → End.
- Give every exit condition exactly one sell/close action and ensure a position exists earlier on every incoming path.
- Remove graph loops, fix Balance’s Fail → Stop bot path, and resolve locked nodes or missing notification destinations.
A running bot has no trades
Inspect the candidate funnel and most recent source timestamp. No observed signals, blocked candidates, attempted orders and confirmed fills are different states.
A confirmation threshold, stale feed, missing flow coverage, empty wallet list, token filter or entry chase limit may legitimately reject candidates. Do not remove safeguards just to force a trade.
An action is pending or uncertain
Check the owned Ledger position and task receipt before retrying. A pending or uncertain result does not prove that a trade never happened.
Avoid a duplicate sell, buy or new action identity until the first result is reconciled. If an Orbi is stuck repairing a graph, ask for a report on its current blockers and the saved graph state.
No notification arrives
Confirm the destination is connected to this account, the graph is saved and running, and the branch comes from a successful event.
For company sources, check collector coverage, chosen tickers, importance and freshness. For fills, wait for confirmed execution. Historical data and missing fields are not fabricated as fresh alerts.
A live feature is unavailable
Follow the feature’s release status in the app. Manual trading can be marked Coming soon; paper availability does not mean a live route is enabled.
Withdrawals retain their own confirmation requirements even while signup verification is paused. If confirmation delivery is unavailable, do not bypass the protection or repeatedly submit a transfer. Contact support with the visible error and time, never your credentials or wallet secret.