Business workflow guide
How to stop ChatGPT dots work: pause, tasks and schedules
AI-assisted guidance prepared for Blue Canvas from the official sources linked below. The examples are proposed tests, not reports of firsthand product testing.
If a dots task is using the wrong brief, pause the work you can identify and inspect what else is running. One stopped conversation is not evidence that every delegated task and future run has stopped.
Use the control for the work you want to stop
OpenAI distinguishes three controls: Pause for the dot's current main task, Activity for inspecting and stopping a delegated task, and Scheduled for disabling or deleting a recurring task. Resume continues a paused dot. Stopping work does not undo actions already completed.
| Your aim | Control to inspect | What remains to check |
|---|---|---|
| Interrupt the current main task | Pause | Delegated tasks and future schedules |
| Stop a particular delegated task | That task in Activity | Other related tasks and completed outputs |
| Prevent the next recurring run | The task in Scheduled | Any run already active |
| Reverse a completed change | The affected app or record | A separately authorised recovery action |
Product source: OpenAI's official documentation, checked 16 October 2026.
Contain the task without creating more work
Start by naming the problem and the affected responsibility. For example, a fictional supplier briefing may be using a retired source folder. Requesting 'fix everything' at that point can make the scope harder to follow. First establish which task, output and destination are involved.
Our suggested recovery record is deliberately plain: task name, observed problem, source involved, last inspected result and current status. Do not paste passwords, private customer records or unnecessary personal details into it. Keep evidence in the appropriate business system and link only what the reviewer is allowed to see.
Adapt this example to your approved task
Stop work on [specific responsibility]. Identify its active delegated tasks and recurring schedules, and report their current states. Do not delete files, send corrections or undo completed changes. List any actions already completed and any state you cannot verify. Wait for my decision before restarting or taking a recovery action.
Check active work and the next scheduled run separately
Open the relevant task and inspect its status rather than relying only on the main conversation's summary. Record what you can see and where verification is incomplete. If several similarly named tasks exist, match the source, purpose and destination before stopping or disabling one.
Next inspect the schedule tied to that responsibility. Check its instructions and timing, then confirm the intended future run is disabled if that is your decision. Do not remove unrelated recurring work to simplify the list. For a reversible pause in a pilot, disabling a schedule may be more appropriate than deleting its configuration.
Inspect completed actions before attempting recovery
Separate an unsent draft from a message already delivered, and a proposed file change from a saved change. Look at the destination system where you are authorised to do so. Record an unknown state as unknown; silence from the dot is not evidence that nothing happened.
Prepare any correction as a separate action with its own scope. That may mean asking the record owner to review an earlier edit or preparing an explanatory message for approval. Do not automatically resend a message because its delivery is uncertain, and do not assume rolling back one file reverses a wider workflow.
Closing a call or disconnecting a device is not the same job
OpenAI says ending a voice call does not necessarily stop assigned work. The computer documentation also distinguishes an offline device from revoked access. These are reasons to inspect task controls rather than using the end of a conversation or a disconnected laptop as a stopping procedure.
A whole-dot deletion is a different, irreversible decision. OpenAI advises reading the deletion confirmation and saving needed results first; deletion does not recall delivered messages or reverse connected-app changes. Do not use deletion as a quick substitute for identifying one unwanted task.
Product source: OpenAI's official documentation, checked 16 October 2026.
Product source: OpenAI's official documentation, checked 16 October 2026.
Product source: OpenAI's official documentation, checked 16 October 2026.
Restart only against a corrected brief
- Identify why the wrong work started or continued.
- Correct the source, task instructions or permission boundary involved.
- Choose one harmless sample and name its reviewer.
- State whether the decision resumes one task or reinstates a schedule; do not leave that implicit.
- Inspect the new result and record any unresolved uncertainty before expanding the responsibility again.