Interrupted requests and safe recovery
Determine what completed before deciding whether to try again.
Stop is not rollback
Stop asks the active request to end. It does not undo edits already made in a candidate, delete generated files, revoke a prior Apply or prove that a remote provider stopped charging instantly.
If you stopped deliberately, inspect the terminal status and the candidate before starting another task. If the connection failed, the upstream outcome can be uncertain even when no final answer appeared.
Recovery checklist
- Keep the conversation and draft. Note the last visible activity, error and run state.
- Check whether a candidate exists, what files changed and whether any Apply actually succeeded.
- Inspect the original documents separately; preserve unsaved manual edits.
- Check account usage/reservations if the customer service is available.
- Decide explicitly whether to continue with a new request. Describe existing candidate work so it is not mistaken for an untouched baseline.
Do not click Send repeatedly to recover an uncertain request. A new attempt can produce duplicate work and additional provider usage. Interrupted runs must not silently resume after application restart.
Allowance is still reserved
A reservation is not necessarily a settled charge. When full provider-usage evidence is missing, the service may retain the reservation rather than guessing that nothing was spent. Ask support to inspect the recorded evidence; do not create another paid attempt to test whether the first worked.
Report a useful incident
Include the approximate time, edition/platform, visible model/effort, safe error text and whether Stop was pressed. Say whether there is a candidate, a Preview, an Apply confirmation or unsaved CAD work. Do not send private project files or credentials unless a separately agreed safe process exists.
See support, activity and Review and Apply.