Repository navigation
Scheduled Tasks push/email delivery stops and resumes while metadata remains false/false #51240
Description
Activity
Independent reproduction on ChatGPT Scheduled Tasks (October 11, 2026; times in Beijing/UTC+8), reported with the user's explicit permission.
- In ChatGPT Settings → Notifications, the Tasks category is visibly set to Push. The user has kept this setting enabled and reports repeated missing notifications, not just one occurrence.
- The recurring monitoring task is enabled and executes successfully (hourly condition-watch).
- At 2026-10-11 12:01 Beijing, its monitored event was officially confirmed; the task ran at approximately 12:25 Beijing, detected the event, and produced a completion update in the conversation.
- No proactive push alert was received; the user had to open ChatGPT/check the conversation and ask why there was no notification.
- A task state read after that run returned
is_enabled: true,notifications_enabled: false,email_enabled: false. Important nuance: the user selected Push only, soemail_enabled: falseis expected; the questionable discrepancy is Tasks Push enabled in global UI vs.notifications_enabled: falseon the task, coupled with missing push delivery. - Multiple other active recurring tasks on the same account also expose
notifications_enabled: false; this does not by itself prove the metadata is the cause, especially given the intermittent behavior already reported here.
Expected: When Tasks → Push is enabled and a condition-watch task produces a qualifying update, deliver a push notification, or give a clear per-task opt-out/status. A successful task run should not silently suppress its alert.
Please check: whether global notification preferences are propagated to task records / push subscriptions; whether condition-watch notification dispatch is failing independently of task execution; and whether the exposed
notifications_enabledflag actually controls delivery.I am reporting this as a separate user reproduction rather than creating a duplicate issue. No account identifiers or private task content are included.
Reacted by einattemkin-toughlove
Observed behavior
Scheduled Tasks notifications are completely contradictory and unreliable.
Every task shows:
notifications_enabled = falseemail_enabled = falseYet the actual behavior has been:
Example: a 7 PM Accountability Check-In ran successfully on October 5, but neither the push notification nor the Task Update email arrived.
So the exact same false/false status has meant both “notifications are working” and “notifications are not working.” The metadata is therefore demonstrably contradictory and useless for determining actual notification status.
This is ridiculous for a feature designed to run unattended. Scheduled Tasks cannot be trusted if users must manually check whether every task ran because its success notifications randomly disappear.
Expected behavior
Scheduled Task push/email delivery should be reliable, and the exposed notification metadata should accurately reflect whether those delivery channels are enabled and functioning.
Please investigate both the intermittent push/email delivery and the false/false metadata that does not reflect actual behavior.