My Agent Looks Stuck or Still Processing After a Power Outage or Disconnection — How Do I Resume?

Last updated: April 27, 2026

When your internet drops or your power goes out while an agent is responding, the chat may appear frozen or stuck on a loading spinner after you come back. The agent is almost certainly no longer running — refresh the page and send a new message in the same conversation to pick up where you left off.

Symptoms

  • You return to your agent chat after a power outage, browser crash, or internet disconnection and see a loading spinner or "processing" indicator.

  • The agent appears to still be generating a response, but nothing new is appearing.

  • You're unsure whether the agent is still running and consuming credits.

Cause

When your connection is interrupted while an agent is streaming a response, the backend detects the disconnection and attempts to reconnect for about 30 seconds. If your device doesn't reconnect in that window, the agent's session is marked as FAILED and execution stops.

However, if you reopen the page without refreshing, your browser may still display the last UI state from before the interruption — typically a loading spinner or "processing" indicator. This is a stale visual state, not a live process. The agent is no longer running, and no additional credits are being consumed.

How to Resume

  1. Refresh the page — press Ctrl+R (Windows/Linux) or Cmd+R (Mac). When the page reloads, the frontend fetches the actual interaction state from the backend. If the agent has stopped, the chat will show as idle instead of processing.

  2. Send a new message in the same conversation. The agent will pick up with your full message history and all workspace files (spreadsheets, CSVs, images, etc.) intact. You don't lose any prior context.

What If the Chat Still Looks Stuck After Refreshing?

If the agent's background process hasn't finished winding down yet (rare, but possible), refreshing may still show a processing state. In that case:

  • Wait 1–2 minutes and refresh again. The process will complete on its own.

  • If it persists, start a new conversation with the same agent. Your workspace files will carry over to the new session automatically, though the previous message history won't be included.

Frequently Asked Questions

Is the agent still consuming credits while it looks stuck?

No. Once the backend marks the interaction as FAILED due to disconnection, the agent stops processing and no further credits are charged. The agent execution is tied to the backend task, which terminates independently of your browser connection.

Will my files and conversation history be lost?

No. Conversation history is preserved within the interaction and is fully loaded when you send a new message in the same chat. Workspace files — any files the agent created or you uploaded — persist across conversations for the same agent.

Do I need to re-upload files or re-explain context?

Not if you continue in the same conversation. The agent automatically receives your full prior message history and retains access to all workspace files. Just send your next instruction as if the interruption never happened.

Related Docs

Still Need Help?

If this didn't resolve your issue, reach out to support at support@gumloop.com.