What issue are you seeing?
Recurring Scheduled tasks in ChatGPT Work on the web are sometimes changing from enabled to paused after a scheduled run, without any user request to pause, disable, delete, or reschedule them.
In the latest occurrence, four unrelated recurring tasks were found disabled shortly after their runs. Other recurring tasks remained enabled, so this was not an intentional global pause.
The saved prompts did not authorize schedule mutation. Some prompts contained session gates such as “exit silently” or “do nothing” when a condition was not met. Those instructions were intended to end only the current run, not pause the recurring task. A separate affected recurring report did not contain such a gate.
Restoring the tasks by setting is_enabled: true succeeds, but the unauthorized pausing has recurred.
What steps can reproduce the bug?
- Create and enable multiple recurring Scheduled tasks in ChatGPT Work on the web.
- Give some tasks durable prompts that may end one run early when a condition is not met, without instructing ChatGPT to change the task or schedule.
- Allow the tasks to run unattended.
- Inspect the Scheduled view or automation state after the runs.
- Observe that some recurring tasks have changed to Paused /
is_enabled: false without user authorization.
The failure is intermittent rather than affecting every task on every run.
What is the expected behavior?
A recurring task should remain enabled after every run unless:
- the user explicitly pauses or deletes it;
- its recurrence rule has completed; or
- a documented system policy suspends it and clearly reports the reason.
An instruction such as “exit silently” or “do nothing” must end only the current run. It must never be interpreted as permission to pause the recurring automation.
Failed, blocked, or no-op runs should be recorded in run history without mutating is_enabled.
Additional information
- Product surface: ChatGPT Work / Scheduled tasks on the web
- Impact: unattended workflows stop silently and miss subsequent runs, requiring repeated manual recovery
- Related UI symptoms observed during the recurring failures:
Content failed to load, conflicting active/paused states across views, and a duplicate task entry
- Private task names, prompts, task IDs, account details, and workflow data are intentionally omitted
What issue are you seeing?
Recurring Scheduled tasks in ChatGPT Work on the web are sometimes changing from enabled to paused after a scheduled run, without any user request to pause, disable, delete, or reschedule them.
In the latest occurrence, four unrelated recurring tasks were found disabled shortly after their runs. Other recurring tasks remained enabled, so this was not an intentional global pause.
The saved prompts did not authorize schedule mutation. Some prompts contained session gates such as “exit silently” or “do nothing” when a condition was not met. Those instructions were intended to end only the current run, not pause the recurring task. A separate affected recurring report did not contain such a gate.
Restoring the tasks by setting
is_enabled: truesucceeds, but the unauthorized pausing has recurred.What steps can reproduce the bug?
is_enabled: falsewithout user authorization.The failure is intermittent rather than affecting every task on every run.
What is the expected behavior?
A recurring task should remain enabled after every run unless:
An instruction such as “exit silently” or “do nothing” must end only the current run. It must never be interpreted as permission to pause the recurring automation.
Failed, blocked, or no-op runs should be recorded in run history without mutating
is_enabled.Additional information
Content failed to load, conflicting active/paused states across views, and a duplicate task entry