When a Bot does not reply
Answer a few questions in order. Each one either sends you to the next or tells you the fix.
3 min read
1. Does the status page say the workspace is running?Copy link to this section
Open the status page. Every step should be ticked and the workspace marked as running.
2. Is a model key in place and does it pass its test?Copy link to this section
An administrator can check under Admin › Credentials › Model providers and choose Test key. Without a working key no coworker can think, so none replies.
3. Is the Bot paused for spending?Copy link to this section
A banner in the conversation and on the Bot's profile says so, and its Monthly budget panel reads Paused for spending. A personal or daily cap refuses your own next turn instead; Settings › My usage shows yours.
4. Is it waiting for you?Copy link to this section
Look for a dot on Computer in the chat header, a card in the conversation, or a number on Approvals. A Bot that has asked for approval, a password or your help stops until you answer.
5. Is the model provider answering?Copy link to this section
If Test key passed a moment ago but replies still do not come, or stop part-way with an error, the provider may be slow or down. Check the provider's own status page.
Fix: the workspace is not runningCopy link to this section
The status page names the step that failed. Find its message in Troubleshooting, which gives the cause and what to do. Nothing a Bot is asked can run until the workspace is up.
Fix: add or replace the model keyCopy link to this section
Ask an administrator to add a key, or Replace key if the test fails, as in Getting started. A key can stop working when it is revoked, expires or runs out of credit with the provider. If the Bot uses a model of its own, its provider needs a key too; see Model providers.
Fix: the Bot reached a capCopy link to this section
Choose Ask for an overage on the paused Bot, or ask an administrator to raise the cap. It also starts again by itself on the first of next month (UTC), and a daily cap at midnight UTC. Details are in Budgets and cost control.
Fix: answer what it askedCopy link to this section
Approve or deny the request, enter the password it asked for, or take control and hand back. A request nobody answers expires, and the Bot is told so. See Approvals and boundary rules and The Bot's computer.
Fix: wait for the provider, or switchCopy link to this section
Send the message again once the provider recovers. If your workspace has keys for more than one provider, an administrator can choose another as the default, or give this Bot a model of its own, as described in Model providers.
Still nothingCopy link to this section
Start a new conversation with the Bot and send a short message. If that is answered, the old conversation was stuck on a step: say “continue” there, or start the task again. If not, send your administrator the conversation's link and the time you sent the message; the operations page and the audit trail show what happened to it.
Last updated