Failed or stuck Ampere session

An Ampere session can sometimes take longer than expected, lose connection to its session workspace, or show that a response did not finish. Your session history is still the best place to start. Keep the session open long enough to see whether Ampere finishes, asks for input, or shows a recovery message before you start the same work again.

Do not send the same prompt repeatedly while Ampere still appears to be working. That can create duplicate work or make it harder to tell which response is current.

Stop a response that keeps running

If Ampere has been working longer than expected and you want to stop the current response, select Stop generating in the composer.

If the stop request does not confirm right away, leave the session open and wait for the session to settle. The response may still finish, move into a stopped state, or show a message that tells you what to do next.

If Ampere shows a recovery action such as Reopen Workspace, use that action before you resend the original request. If the app says the previous response is still stopping, wait a moment and try the recovery action again.

Reopen the session and review what finished

Open Sessions, then select the session again. If the session opens, review the latest response and any visible outputs before you decide what to do next.

Check for three things:

1. A final answer or partial answer in the transcript.
2. Files or outputs in the session workspace that may have been created before the issue appeared.
3. A visible next step, such as retrying, restarting the session workspace, answering a question, or starting a new session.

Ampere recovery is best effort. A reopened Workspace may let you continue, but it does not guarantee that every in-progress step can be resumed. If the previous response is incomplete, ask Ampere to continue from the visible context or start a new session with a short summary of what already happened.

Use Diagnostics when the session still needs help

Each Ampere session has a Diagnostics action in the session header. Open it when a session does not recover, when support asks for troubleshooting details, or when the app shows a session workspace connection message.

Diagnostics can show the session and Workspace identifiers needed for support review. It can also run a lightweight session-workspace health check. If the health check offers a session workspace fix, use it before you retry the same request.

Use Copy details when you need to send context to support. Do not paste passwords, private tokens, billing details, or unrelated customer data into your support message.

Retry safely

Retry only after the current response has stopped, finished, or clearly moved into a recovery state. When you retry, make one change that helps Ampere continue cleanly:

• Ask Ampere to continue from the last visible result.
• Summarize what finished and what is still needed.
• Attach or reference any output file that was created before the issue.
• Start a new session in the same project if the current session will not reopen.

If the original request was very broad, split it into a smaller next step. For example, ask for an outline first, then ask Ampere to create the file, deck, image, or report after the direction is clear.

Contact support

Contact support when the same session will not recover, the response keeps running after you try to stop it, the session workspace fix does not work, or important outputs are missing after the session settles.

Include:

• The session title and project name.
• The approximate time the issue happened.
• What you asked Ampere to do.
• What you expected to happen.
• What you saw instead, including any visible warning.
• The copied Diagnostics details.

That context helps support investigate the specific session without asking you to recreate the problem from memory.