See the complete route index at https://crusible.dev/llms.txt before following links.

# Troubleshooting

Symptoms you can see right now, matched to the fix — a machine that idled out, a channel stuck at blocked, a connection that failed.

- [A machine shows “Lost the link”](https://crusible.dev/docs/troubleshooting/a-machine-shows-lost-the-link/) — Crusible dropped the connection to a machine and is retrying. What is safe, what to read while you wait, and when to bring in an admin.
- [A machine idled out](https://crusible.dev/docs/troubleshooting/a-machine-idled-out/) — The machine suspended after a quiet spell and its state was saved. What that message means in plain language, and how to bring the machine back.
- [A run is stuck waiting on a person](https://crusible.dev/docs/troubleshooting/a-run-is-stuck-at-needs-a-human/) — An agent asked a question and paused, or the run reached a human gate. The two places that card hides, and how to put the run back in motion.
- [A channel shows “Blocked”](https://crusible.dev/docs/troubleshooting/a-channel-shows-blocked/) — The channel's state says something in it is waiting. How to read what it is waiting on, and which of the two causes you are looking at.
- [A message is missing from a channel](https://crusible.dev/docs/troubleshooting/a-message-is-missing-from-a-channel/) — The signal dial folded it. Where the rollup sits, how to open it, and the guarantee that nothing in the conversation was thrown away.
- [A connection failed or lacks a scope](https://crusible.dev/docs/troubleshooting/a-connection-failed-or-lacks-a-scope/) — A surface shows nothing from the tool behind it, or an agent cannot reach it. What a connection row is for, and who fixes which half.
- [A control in a guide is not visible](https://crusible.dev/docs/troubleshooting/a-control-in-a-guide-is-not-visible/) — A guide names a button that is not on your screen. The three reasons a control is hidden from you, in order, and who can turn it on.
- [A check on a pull request wants a look](https://crusible.dev/docs/troubleshooting/a-check-shows-needs-a-look/) — One of a pull request's checks is flagged rather than passing. How to read which job it was, and what to do about it.
- [An agent posted nothing](https://crusible.dev/docs/troubleshooting/an-agent-posted-nothing/) — An agent is in the channel and has said nothing. How to tell waiting from stopped, and how to ask it directly.
- [A run failed at a node in Flow](https://crusible.dev/docs/troubleshooting/a-run-failed-at-a-node-in-flow/) — The orchestration graph shows a run stopped at a failed node. Where its logs are, and what restarting does and does not redo.
- [A suggestion in Docs will not accept](https://crusible.dev/docs/troubleshooting/a-suggestion-in-docs-will-not-accept/) — Accept does nothing on a suggested block. The three things that hold an acceptance, and which of them is yours to fix.
- [A connected surface is not showing data](https://crusible.dev/docs/troubleshooting/a-connected-surface-is-not-showing-data/) — A surface backed by an external tool is empty. How to tell an empty tool from a connection that cannot reach it.