An approval is specific
A Work action card identifies the resource, proposed values and warnings. Approval applies to that exact target and those arguments. It does not authorize every recommendation in the conversation, all future actions from a plugin, or unrelated changes on the same page.
Read Before and After together. Confirm which account or deployment will be affected, whether the action touches a draft or a public resource, and whether it can start spending or messaging. Cancel a preview that contains assumptions you have not approved.
Read the status, not just the animation
| Status label | What it means | What to do |
|---|---|---|
| Awaiting your approval | A change is prepared, not executed. | Review the target and values. |
| Approved · queued | Approval is stored; work is waiting. | Wait or cancel pending work when offered. |
| Checking current permission and version | Access and the reviewed resource are being rechecked. | Do not submit a duplicate. |
| Execution started · checking result | The effect may be underway. | Refresh its saved status if necessary. |
| Verified complete | The result was verified for the stated scope. | Open the affected resource. |
| Provider accepted | The provider accepted a request; final completion may still be pending. | Check the provider or follow-up read. |
| Outcome unconfirmed · do not repeat | An attempted action has no confirmed result. | Inspect before attempting anything again. |
Messages use their own accepted and delivered states. A deployment build can also become ready before anyone has checked the public browser experience. Match the proof to the claim.
Expiry and changed versions
Approval can expire. A resource, selected account or connection can also change between preview and execution. Work stops rather than silently applying old instructions to a new state. Read the current object again and prepare a fresh proposal.
Refreshing a saved status retrieves the existing receipt; it does not renew an expired approval or replay an external action. Use the explicit refresh control when the network disconnects or the page appears stuck.
Plans, cancellation and closing the drawer
A saved plan can continue authorized reads and prepare later steps after a verified result. Each mutation still pauses for its own approval. An approved queued operation may continue when the page closes; hiding the drawer is not a cancellation command.
Cancel pending action stops work that has not started when the control is available. It cannot recall an email already accepted by its provider, undo completed DNS changes, or reverse an in-flight advertising request. Review the actual status after cancellation.
Undo is not universal
Some local task types may offer a preview of an undo. Others do not. An internal lead note cannot be deleted through the documented Work note action, and an archived Close Forge deployment cannot be restored through Work. Never interpret a generic cancel button as rollback.
For a completed unwanted change, inspect the resource and its history. Prepare a supported compensating change or use the owning app/provider. Keep the operation reference so support can distinguish the original effect from any attempted correction.