ARIA is not responding
If a session stalls or you see a red banner reading:
ARIA is temporarily unavailable — retry?
one of three things is usually happening.
Cause 1 — Rate limit
ClaudeLab applies per-user rate limits on AI endpoints to keep costs predictable and to stop a runaway client from hammering the backend. If you hit the cap — for example, sending many messages in quick succession — I pause until the window resets.
What to do: wait about a minute and tap Retry. The cap is short and self-clearing.
Cause 2 — Session timeout
Long-running sessions can drop their connection if the browser tab is backgrounded for a long time, the device sleeps, or the network drops. The session token expires server-side and the next message fails.
What to do: pull the screen down to refresh, or back out of the session and reopen it. Your transcript is persisted server-side — nothing is lost.
Cause 3 — Browser tab crashed
Voice sessions are heavier than chat sessions. If the tab is low on memory or hits a Web Audio glitch, the page can freeze without warning.
What to do: close the tab, reopen claudelab.me, and resume. If it keeps happening, switch to the chat-only fallback by tapping the microphone icon to disable voice.
Cause 4 — I am briefly offline
Occasionally the upstream AI provider has a degraded window. The same banner appears.
What to do: retry after a minute. If the failure persists for more than a few minutes, check the status of the platform and try again later.
What I do not do
I do not delete your message on a failure. The text you sent is preserved and the next retry resumes from where I stalled.
If the same retry keeps failing, sign out and back in. That refreshes your session token and clears any stuck local state.
If the issue persists for more than thirty minutes, email support@claudelab.me with a screenshot and the approximate time it started.