Agent
Recover an interrupted Agent response
Check uncertain sends, preserved activity, failed answers, and retries without blindly repeating changes.
A connection problem can hide the result of a request that the server already accepted. Check the saved conversation and affected content before repeating an action.
When sending was not confirmed
- Keep the current chat open and read the notice.
- Select Check response status when offered.
- Wait for the check to finish.
- If the response appears, continue reviewing it rather than sending a copy.
- If CareMap says the message has not been recorded, review the restored draft and send it again when ready.
While status remains uncertain, Send is disabled. The current draft and selected files are retained in that open experience. This is not a guarantee that an unsent draft survives a reload, account change, or workspace change.
The built-in retry can reuse the original send attempt. Starting a fresh request in another chat does not provide the same protection against repetition.
When a saved response failed
An interrupted entry can preserve your message, progress, completed tool results, and sometimes an unfinished answer. Read its warning before continuing.
- Length limit: ask for a shorter answer or split the request.
- No answer or provider failure: inspect saved activity, then ask only for the remaining work.
- Response in progress: wait briefly and reopen the same chat.
- Could not finish recording: inspect saved activity and the affected content before retrying; a missing final answer does not prove no work occurred.
- Provider funding unavailable: an administrator must restore the external provider's funding. Your own CareMap credit balance can still be positive.
A displayed Retry request can resend a retained draft. If there is no retained draft, it can reload the chat instead. It is not a universal undo or repeat-last-message button.
When a stopped response has partial work
Response stopped ends that response, not the effects of completed tools. Check the saved activity and any changed Guide, Form, Note, or schedule. Continue with a clear request for what remains.
Do not treat Waiting for the tool result or an interrupted-tool warning as proof that the action succeeded or failed. Check its destination.
Missing history or changing access
Verify the account, workspace, and search query. History loads only a limited collection; see conversation management.
If a remembered chat was deleted or is no longer available, choose another history entry or New chat. A network restore error can instead be retried by reloading after preserving unsent text.
Get help with a persistent failure
Expand Support details when available. Record the visible message, request ID, time, workspace, and whether a change actually occurred. Share only the details appropriate for your support channel. See availability and funding for credit-specific problems.