Troubleshooting

Start with Activity in the sidebar: it lists every run, with filters for runs that failed or are waiting on you. Open a run to see what happened. You can also ask any bot: "why didn't my routine run?"

A bot isn't answering

It shows Working…: it's still on the task. Keep chatting, or choose Stop.
A card is waiting: answer the question or approval card in the chat. After 4 hours you get a reminder; after a day the run stops with Stopped. This was still waiting for an answer.
An error shows in the chat: find it below.

Message	What to do
Out of credits. Top up in Billing to keep going.	Choose Add credits or a bigger plan in Settings → Billing. See Account and billing.
Out of credits. Ask a team owner to top up.	Only the team's owner can add credits.
Your team's plan has ended. Ask a team owner to renew it.	The owner renews it in Settings → Billing.
You've used this month's free messages. Upgrade in Billing to keep going.	Wait for next month or choose a plan.
This bot or routine is paused on the Free plan. Upgrade in Billing to use it.	The Free plan runs a limited number of bots and routines; the newest ones over the limit are paused. Archive one or choose a plan.
Your own model needs a paid plan. Upgrade in Billing.	On Opisense Cloud, your own model connections work on paid plans.
Connect a model to start a run.	Connect one in Settings → Models. See Models.
This month's computer allowance is used up.	Computer time resets each month, or choose a bigger plan. The Free plan includes none, so bots there can't start their computer.
This conversation is too long for the model…	Choose Clear conversation in the bot's settings; its memory stays. Or pick a model with a larger context.
… is rate limiting requests. Try again shortly.	The model provider is busy. Add a fallback model in Settings → Models so bots switch on their own.
This person is no longer a member of this space.	The work was queued by someone who has left.

A routine didn't run

Open Routines in the bot's settings and check it's Active. Routines from the Marketplace or an import start Paused.
Open Run history. Failed shows the error; No reply means it ran but had nothing to post. A routine that watches for changes stays quiet when nothing changed, unless Post "No changes" in chat is on.
Check that it has a trigger, and that a run isn't waiting on an approval card.
Wrong time? Each routine keeps the timezone it was made in. If yours changed since, ask the bot to recreate the routine.
Choose Test run to try it now.

See Routines.

A bot can't use an app

Not connected yet: ask "connect my GitHub" and choose Authorize. On a team, each person connects their own apps, even for a shared bot. See Connect apps.
The sign-in expired: open the app in Integrations and choose Reconnect.
Wrong account: tell the bot which one to use, or choose Add account on the app's page.
In another space: connections stay in the space you made them in. Connect it again here.
Turned off for this bot: check Tools in the bot's Advanced settings.
Blocked: a Block rule in Settings → Approvals refuses it without asking.
An MCP server: open Manage MCP servers and choose Test connection.

A bot forgets things

Earlier in a long chat: a bot keeps the recent part of the chat in view and searches older messages when it needs them. Anything that must always apply belongs in its instructions; facts belong in its memory: "remember that invoices go to Finance".
What it wrote down is wrong: open Memory in its settings and fix or delete the note.
Another bot knows it, this one doesn't: each bot has its own memory. Put facts all your bots need in shared memory.
A teammate told the shared bot: memory is per person, also for shared bots. Put team-wide rules in the bot's instructions. See What's shared in a team space.

A bot does the wrong thing

Turn on Show tool activity in Settings → General under Advanced, and see what it did.
Tell it what was wrong and have it fix its instructions. Instruction history restores an earlier version.
If it picks the wrong app or mixes up jobs, give it fewer apps or split it into two bots. See One bot or several.
For hard, multi-step work, try a stronger model or a higher Thinking level in its Advanced settings.

See Write good instructions.

The bot's computer misbehaves

Open the computer and choose More computer actions: Recover computer recreates one that isn't working, and Reset computer goes back to the last saved workspace. When the header shows Needs you, the bot is waiting for you to do a step on its screen, such as a CAPTCHA. See The bot's computer.

A chat app doesn't reach the bot

Not linked: link it in Settings → Messaging, and send the code within 10 minutes.
In a group: approve the group under Requests. With Mentions only, mention the bot.
No Messaging in Settings: your server has no chat app set up.

See Chat apps.

Still stuck

Email support@opisense.com with the bot's name, roughly when it happened and the message you saw. Never send passwords or keys.