Understand Ampere resume and recovery

Ampere sessions can sometimes be interrupted by a session workspace restart, browser refresh, connection issue, or long-running task that does not finish cleanly. Ampere keeps the chat, visible outputs, Workspace files, and session controls together so you can review what happened and continue from the safest point.

Recovery is best effort. It can help you return to a session and continue from visible context, but it does not promise that every in-progress action can be resumed exactly where it stopped.

What resume means

Resume usually means returning to an existing Ampere chat and continuing from what is visible there. The transcript, latest response, suggested follow-ups, Workspace files, outputs, and session title are the first things to review.

If the chat reopens cleanly, read the latest Ampere response before sending another prompt. Ampere may have already finished part of the work, created a file, asked for input, or left a clear next step.

What recovery can do

Recovery can help Ampere reconnect a session, restart a session workspace when the app offers that action, or give support the diagnostic details needed to investigate a specific chat.

Because recovery is best effort, check the visible state before assuming work was lost. A session may contain a partial answer, a completed file, a usable output, or enough context for Ampere to continue. If the previous task did not finish, ask Ampere to continue from the last visible result instead of starting the same request from scratch.

What to review before continuing

Before retrying or starting a new session, check:

• The latest message from Ampere.
• Any visible status, warning, or recovery action in the session.
• Files and outputs in Workspace or Outputs.
• Whether Ampere is waiting for your input.
• Whether the result needs a smaller follow-up prompt rather than a full rerun.

This review helps avoid duplicate work and makes it easier to decide whether to continue, revise, or contact support.

When to use Diagnostics

Use Diagnostics when a session does not recover, support asks for details, or the app shows a session workspace connection issue. Diagnostics can expose the identifiers and session-workspace health information support needs to investigate that specific session.

Only share the troubleshooting details support asks for. Do not paste passwords, private tokens, billing details, or unrelated customer data into a support message.

When to start fresh

Start a new session when the old session will not reopen, the visible context is too incomplete to continue, or you want to give Ampere a cleaner smaller prompt.

If the work belongs to the same campaign, client, product, or launch, start the new session from the same project. Include a short summary of what already happened and attach or reference any useful file that was created before the interruption.

Where to go next

For the main Workspace tour, read Tour an Ampere session. If a session is actively stuck or not recovering, use Failed or stuck Ampere session. If an expected output or file is missing, use Missing output or Workspace file.