Start with the saved state
Before repeating a request, check whether you have an analysis, a prepared proposal, an approved queued operation, an executing action or a completed result. Those are different states. The animated drawer is not the authority for what happened; the saved task and provider receipt are.
Keep the workspace, app, exact target and operation or file reference. A concise description of the stage that failed is more useful than “AI is broken.” Never include credentials, session cookies or unnecessary customer information in support messages.
Work is missing or an action is unavailable
Confirm the signed-in user and workspace, Intelligence access, Work availability and the app required by the action. Team permissions for viewing, editing, lifecycle changes and managing connections can differ. A plugin does not grant a missing app or role.
Ask an administrator to resolve the specific access issue. Do not create another account, use a teammate’s token or broaden provider permissions as a workaround. Some gallery tiles are intentionally Coming soon; some app tasks require an owning-app handoff.
The target or version changed
Read the resource again and prepare a new preview. Work uses the exact reviewed record/version so it does not overwrite a newer edit without review. For saved Close Forge recommendations, recover the original analysis in the original conversation; do not silently apply it to the page you happen to have open now.
Changing a connection, resource selection or provider tool definition can also invalidate a preview. Reconfirm scope before making another proposal.
The browser closed or the request timed out
An approved queued operation may continue after the page closes. Reopen the saved operation and use Refresh saved status. That reads the receipt instead of repeating the external action.
If a checkpoint or continuation control is offered, review the remaining work and continue the existing task where supported. Do not assume a fresh prompt resumes the same paid request or knows which prior effects completed.
The provider result is unknown
Stop before retrying. Inspect the affected provider object and saved operation. A request may have been accepted even if the response did not reach the browser. Duplicating a send, ad change or deployment can create a second effect.
Report the uncertainty accurately: “The action was attempted; completion is unconfirmed.” Avoid saying either “nothing happened” or “done” without evidence. A failed read after an action is not proof that the action failed.
A file is queued or a report is incomplete
Wait for the file’s actual saved state and use its returned link. Do not treat code or a proposed filename as a deliverable. For incomplete data, narrow the query or follow supported continuation while preserving the account and period.
Do not sum sampled search rows into a company total. Ask for a verified report source or a clearly labeled partial answer.
Give support a useful handoff
- Workspace and app names, plus the intended record or selected provider account label.
- Task/operation/file reference and the time the problem occurred.
- Visible status and non-sensitive error wording.
- What you expected, what you observed and whether you already retried.
- For external changes, what the provider currently shows.