We lost track of Runner’s reply. Refresh the page to get it back.
Resolve Runner errors for runner stopped or its reply is missing: meaning, safe recovery steps, and how to verify the result.
Runner stopped or its reply is missing
Messages you may see
Couldn't retry this response. Try again.Couldn't switch responses. Try again.This conversation changed. Reloading the latest version.Runner can't run multi-step plans right now. Try again in a bit.Runner hit a problem on our side and stopped. Try again. If it keeps happening, contact support.Runner couldn't get started on this. Nothing changed — try sending it again.The AI behind Runner dropped out mid-response. Try again in a moment.Runner didn’t answer that one. Send it again.We lost track of Runner’s reply. Refresh the page to get it back.
A failed response does not prove that every action in that response was undone. Check task details and the affected result before repeating work.
- Read the latest message and task details in the original conversation.
- If Runner lost track of a reply, refresh to recover it before sending again.
- If no work started or the AI response failed, wait a moment and retry once after checking for completed work. If response selection reports a conflict, let the current run settle and use the refreshed conversation before switching responses. If multi-step plans are unavailable, wait before retrying that command.
- If Runner repeats the failure, contact support with the conversation URL, error, time, and last visible task state.
Check: The recovered reply appears or the task proceeds, and you can verify the requested result in the affected store.
If the error returns
Contact Support and community after one appropriate retry. Include the exact error, page or conversation URL, workspace/store, approximate time, and what you checked. Remove sign-in codes, credentials, payment details, and customer information.