When something looks stuck

The four states that look broken, what each actually is, and the fix that works.

The steps

Hiring seems to hang — Provisioning builds a whole workspace — memory, files, configuration — and can take a moment. The working screen is normal. If the employee still hasn't appeared on **Employees** after a few minutes, refresh once; if it's truly absent, hire again — you were never charged for a ghost.
An app shows connected but behaves disconnected — Authorizations expire; the label can lag. The test is functional, not visual — ask the employee for something only the live account knows. If it can't answer, disconnect and reconnect the app on the **Apps** tab. That resolves most of these.
A run is taking long or came back empty — Minutes are normal — it's producing a document, not a reply. If a run comes back empty or visibly wrong, don't relaunch the same form: tell the employee in chat what came out and what you expected. It can see its own run and usually fixes it on the second pass.
"Credit limit reached" — Not an error — the spending cap you (or the plan) set doing its job. Check usage and raise the cap at **Settings → Billing**, or wait for the cycle. Employees resume where they stopped; nothing is lost.
None of the above — Send feedback from the sidebar — it attaches the technical context automatically, so "the page did nothing when I clicked" is enough for us to find it. A human reads every report.

The stuck thing identified as one of four known states — or reported with enough context to be fixed.