Skip to content
Independent guide · Get Started & Trust

How to Pause Dots and Stop Delegated or Recurring Tasks

Pause the dot, stop a delegated task, and cancel recurring work separately.

Updated 4 October 2026 · Independent of OpenAI

OpenAI’s controls distinguish the main dot, its delegated tasks, and scheduled tasks. Pausing the main task does not cancel every other task or future schedule.

Pause the dot, stop a delegated task, and cancel recurring work separately. A successful workflow ends with something you can verify, not merely a confident summary. Keep the proof and the proposed action side by side.

Define the task

What to prepare before you begin

Specify the task name and whether it is scheduled or delegated and the decision you are trying to make. That keeps the work from expanding into an unreviewable search.

A useful deliverable

Correct task stopped, schedule disabled if needed. Ask for the most consequential assumption to be highlighted at the top instead of buried in a footnote.

Worked situation

How this plays out in practice

Pausing a conversation, stopping a current task, and deleting a Friday schedule solve different problems. A recurring task may start again if only the current run is stopped. If a polished response skips this complication, it has not solved the task. Ask for a revised result that accounts for it.

Find the named task in Activity and the recurrence in Scheduled. Verify both states after making a change. Keep enough of the trail that a later reviewer can retrace the conclusion when the source changes.

A practical sequence

Run a bounded first pass

1. Establish the starting point

Set the source boundary with the task name and whether it is scheduled or delegated and note any item that requires a person to provide access.

2. Request a reviewable draft

Open Activity to find and stop a specific delegated task. Open Scheduled to disable or delete a recurring task. Use Pause for the current main task and Resume when ready. Save a reference to the original material beside each consequential conclusion.

3. Decide the next action

Before moving on, verify the account and the consequence under verify completed external actions separately. Keep approval tied to the exact action.

Editorial judgment

Where a plausible answer can fail

A stopped task cannot retract a message already delivered or undo a file edit. Inspect the target app for any completed effects. The right review starts with the point most likely to change the conclusion, not with proofreading the opening sentence.

Stopping does not undo completed edits or recall messages already sent. Inspect connected apps for changes that need separate reversal. A smaller answer that accurately marks uncertainty is still progress: it tells you what to check next.

Where to go next

Connect this result to the right follow-up

The Get Started & Trust hub gives you the broader route and neighboring tasks. Return there when the present job has produced a result, rather than adding an unrelated responsibility to the same brief. Use the next page as a new brief when its evidence and approval needs differ.

For a closely related outcome, open What Is OpenAI Dots?. That guide focuses on a plain-language explanation of what OpenAI Dots does and how it differs from a single chat. It may use some of the same context, but you should confirm the source and the decision point again. If your next question is about a different angle, How to Set Up Your First Dot is a better fit: create your first dot and give it a bounded task. A new deliverable should have its own date, owner, and acceptance check.

Before you reuse this result elsewhere, look at Dots Privacy, Memory and Permissions for the wider product or review boundary. Take forward the verified facts and leave behind any assumption that was specific to this example. If the source has changed since the draft was made, update the relevant claim first. The purpose of the link is to make the next step more precise, not to imply that every connected guide is needed for every reader.

Adapt this

Build your own task brief

Edit the bracketed information and any sentence that does not fit your account. This is a suggested workflow, not a promise that your dot has access to a particular app or feature.

Your review

Check before moving on

Tick what you have actually checked. Your progress stays on this device for this page and can be cleared at any time.

0 of 4 checked

Questions

Frequently asked questions

Where should I verify this feature?

Use the scenario on this page as a small test. Find the named task in Activity and the recurrence in Scheduled. Verify both states after making a change. Keep a source and a date beside any detail that can change.

What information matters most for how to pause dots and stop delegated or recurring tasks?

Start with the task name and whether it is scheduled or delegated. OpenAI’s controls distinguish the main dot, its delegated tasks, and scheduled tasks. Pausing the main task does not cancel every other task or future schedule. Give the exact source or account where a decision depends on it.

What changes when a connected app is involved?

Stopping does not undo completed edits or recall messages already sent. Inspect connected apps for changes that need separate reversal. The relevant access, audience, and consequences determine what you should approve.

What would a useful result look like here?

Correct task stopped, schedule disabled if needed. It should make assumptions visible and leave a trail to the source, especially for dates, prices, permissions, or changing product details.

What is the common failure in this situation?

A stopped task cannot retract a message already delivered or undo a file edit. Inspect the target app for any completed effects. Review that issue in the actual output instead of treating a polished presentation as proof.

Where can I check the current details?

Follow the official source linked below and inspect your account where access matters. This page was revised in October 2026; availability, terms, and product behavior can change.

Source for current product details: official OpenAI documentation or announcement ↗. The worked situations and briefs on this independent site are editorial examples. Confirm current access and details in your account. Editorial policy.