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.
Find the symptom you are looking at, not the cause you suspect. Every page here starts from something visible in a channel, a machine or a run.
- 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 The machine suspended after a quiet spell and saved its state. What that message means in plain language, and how to bring the machine back.
- A run awaits a person A decision needs an answer, or the terminal has not confirmed the answer you sent.
- 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.
- Huddle audio or connection is not working Check microphone permission, selected devices, speaker output and session access.
- Sign-in or invitation problems Recover a password, replace an invitation link or identify when an organisation owner needs to help.
- A message is missing from a channel Check the destination, folded updates, access and delivery before assuming someone deleted a message.
- A connection failed or lacks a scope Diagnose GitHub installation, repository access and permission refusals.
- A control in a guide is not visible Check the view, access messages and feature availability when a guide names a missing control.
- A suggestion in Docs will not accept Accept does nothing on a suggested block. Check editing access, connection state and whether the proposal is still pending before trying again.
- A connected surface is not showing data Check GitHub source data, freshness and installation access.
