ChatGPT tasks stop sending notifications for one of seven documented reasons: a settings toggle, a missing browser or mobile permission, an auto-paused task, an active-task limit, a model-version bug, or an OpenAI-side incident. Some of those let the task run right on schedule and still produce zero alert, which is the annoying part.
The fast fix: check these four things first
Quick answer: check these four things first, in order.
- Did the task actually run? Open the Scheduled page (or task history) to confirm it fired, versus never running at all.
- Are Push and Email both switched on in Settings -> Notifications?
- Has your browser blocked desktop notifications for chatgpt.com? Look for a blocked-notifications icon in the address bar.
- Have you hit your plan's active-task limit? The Scheduled page shows your current count against the cap.
Here's the part most people miss: a task can run successfully and still send no notification. Those are two separate failures, and only one of them shows up when you check “did the task run.”
As reported by users on Reddit, November 2025, u/Absolut_Ink described exactly this: “Was silently upgraded to 5.1 early November and haven't had push notifications since... All my task are firing in ChatGPT on time but on the backend they are still reading push notifications: false...” The task runs. The notification flag reads false. Nothing in the interface tells you that happened, so you find out the hard way, usually by noticing a report you were counting on never landed in your inbox.
This guide is built on OpenAI's own Help Center documentation, the OpenAI Developer Community, and verified user reports on Reddit and X, each cited with a date, not a hands-on test run by us. (For the general silent-failure framework, see why automations fail silently; this guide stays ChatGPT-specific.)
Why this happens: every documented cause, sourced
Running a daily digest, weekly report, monitoring check, or follow-up nudge through ChatGPT Tasks? Here's every documented cause, no filler:
- The Push or Email toggle in Settings -> Notifications is off.
- Your browser or OS never granted, or later revoked, desktop-notification permission for chatgpt.com.
- Mobile push was never granted, because the prompt only fires when you create or edit a task from the mobile app itself.
- The task auto-paused, because its linked chat was deleted or it sat inactive for a stretch.
- You hit your plan's active-task limit.
- A model-version regression: users report tasks firing on schedule since GPT-5.1 while notifications silently stop.
- An OpenAI-side incident affecting the notification pipeline broadly.
That active-task cap depends on your plan, and OpenAI's own documentation does not fully agree with itself on the higher tiers:
One cause is easy to miss, and it's the one that catches people who keep a tidy chat history. Per OpenAI's Help Center, “If you delete a chat associated with a scheduled task, the task will automatically pause.”
Cause, confirm, fix: the table
Match your symptom, confirm it, apply the fix.
| Cause | How to confirm it | Fix | Source |
|---|---|---|---|
| Notifications off in Settings | Push and/or Email toggled off in Settings -> Notifications | Turn both toggles on | OpenAI Help Center, accessed 2026-08-14 |
| Desktop browser permission missing | Blocked-notifications icon in the browser's address bar | Allow notifications for chatgpt.com in browser site settings | OpenAI Help Center, accessed 2026-08-14 |
| Mobile push never granted | No permission prompt has appeared on your phone | Create or edit a task from the mobile app to trigger it | OpenAI Help Center, accessed 2026-08-14 |
| Task auto-paused | Scheduled page shows the task as paused | Resume it; recreate it if the linked chat was deleted | OpenAI Help Center, accessed 2026-08-14 |
| Active-task limit reached | Scheduled page shows you at your plan's cap | Pause or delete an older task to free a slot | OpenAI Help Center, accessed 2026-08-14 |
| Model-version regression | Run shows in history, but no notification arrives, reported since GPT-5.1 | Resubmit as a fresh task, or fall back to email-only | Reddit r/ChatGPT, Nov 2025; OpenAI Developer Community, Dec 2025 |
| OpenAI-side incident | Multiple users report the same symptom the same day | Check status.openai.com before rebuilding anything | status.openai.com, checked live |
Rows one through five come straight from settings you control. Row six is worth checking first if your task started misbehaving right after an update: it's the only cause with no fix inside your own account.
Platform behavior like this shifts without much warning, which is part of why we track it. Our newsletter covers changes like these as they land.
What's new: the Scheduled page and monitoring tasks (as of August 2026)
As of 2026-08-14, OpenAI's Help Center describes a rollout most guides on this topic don't mention: a dedicated Scheduled page, available on web, mobile, and desktop, with a redesigned creation and editing flow and more flexible scheduling windows.
It also introduces monitoring tasks, a new task type. Per OpenAI's Help Center, monitoring tasks “let ChatGPT periodically check for a change and notify you only when there is something worth reporting,” remembering previous runs so it doesn't repeat itself. For a no-code operator, that's the closest fit yet for a “watch this and tell me only if it changes” job: a competitor's pricing page, a shared doc, an inbox label someone forgot to check. It's a genuinely good idea on paper, assuming the notification actually shows up this time. For a tool-agnostic framework on catching silent failures, see how to monitor your automations properly.
@testingcatalog corroborated the update on X, 2026-06-17: “Scheduled tasks are faster, more reliable, and easier to manage.” The same post reported OpenAI is sunsetting ChatGPT Pulse for Pro users, though that claim traces to the X post alone; no first-party OpenAI page confirms it.
One more line deserves an honest flag, not a guess. OpenAI's own docs state: “Tasks in ChatGPT are supported by all ChatGPT models except Pro models.” Whether that means the Pro plan or a specific Pro-tier model is unclear, and OpenAI hasn't said as of August 2026.
What users are actually reporting (sourced, not our own test)
This section rests on real, dated reports, not a test we ran ourselves.
The clearest evidence sits in the r/ChatGPT thread cited above (Nov 17, 2025). Alongside u/Absolut_Ink's backend-flag report, u/AJP11B posted: “I have daily scheduled tasks that were firing with push notifications all year and now that 5.1 has been released they stopped. Notifications are turned on in all of my settings, but nothing is coming through.” Same platform, same window, independently reported. Two strangers hitting the identical wall in the same week is a stronger signal than one complaint on its own would be.
A different failure mode shows up in the OpenAI Developer Community. In a December 2025 thread titled “GPT-5.1 - Scheduled tasks do not work at all,” a Plus user reported: “They do not run on schedule at all, the prompt to test this; is simple nothing elaborate.” That's execution failing outright, a different symptom than a silent notification miss. The thread auto-closed after 22 hours with no OpenAI staff reply, so don't wait on that forum for a business-critical fix; use the table above instead.
This isn't a one-off, either. A January 2025 Developer Community thread reported the same class of problem on GPT-4o, over a year before GPT-5.1 shipped, with 19 replies and no staff response. @anatolt added light corroboration on X (August 2025):
So the feature is kinda alive, but broken and hidden.
A year apart, two different model generations, the same shrug from support both times.
When to stop relying on ChatGPT Tasks and use a real automation tool
ChatGPT Tasks is fine for a low-stakes, hourly-or-slower, single-person notification. It's the wrong tool once your job needs a webhook (event-triggered, not time-triggered, which OpenAI's Help Center confirms Tasks doesn't support), a cadence faster than once per hour, a guarantee that survives a deleted chat, or reliability someone else on your team is depending on.
If that's you, the honest move is a real automation platform, not another workaround, or a step up to building an AI agent without coding if the job needs more than a simple trigger. Zapier is the fastest no-code setup. Make handles more complex branching at a reasonable cost. n8n gives teams more control, at the cost of a steeper setup.
Before you rebuild anything, check whether this task even needs AI, since a lot of “AI agent” jobs are really a scheduled trigger and a plain rule. And if you're choosing between the two platforms above, n8n vs Zapier for this kind of job is worth reading first.
None of this makes ChatGPT Tasks a bad feature. It's a fit question, not a takedown: light, single-user, forgiving-of-a-missed-run jobs are fine here. Anything a business genuinely depends on isn't, at least not yet.
Frequently asked questions
Why did my ChatGPT scheduled task run but send no notification? Because execution and notification delivery are separate systems. As reported by users on Reddit, November 2025, tasks can run on schedule while a backend flag governing push notifications reads false. Check Settings -> Notifications first, then match your symptom against the cause table above.
Why do ChatGPT tasks stop working after an update (like GPT-5.1)? Users have reported both a notification-delivery drop and a full execution failure tied to the GPT-5.1 rollout, per Reddit and the OpenAI Developer Community. It's a recurring pattern, not a one-time bug: a similar report surfaced with GPT-4o back in January 2025, and OpenAI hasn't published a public root cause for either.
How many scheduled tasks can I have active at once on ChatGPT? Per OpenAI's Help Center, Go gets up to 3 active tasks and Plus gets up to 5. Business, Edu, Pro, and Enterprise are where the documentation disagrees with itself: the main body lists Business/Edu at 10 and Pro/Enterprise at 15, while the FAQ groups all three at 15. Check your own Scheduled page for your actual cap.
Why did my ChatGPT scheduled task disappear or stop showing up? The most common cause is auto-pausing. Per OpenAI's Help Center, deleting the chat linked to a task automatically pauses it, and a task can also pause after inactivity. Check the Scheduled page for a “paused” status before assuming it was deleted.
How do I turn on push notifications for ChatGPT tasks on iPhone or Android? Create or edit a task directly from the ChatGPT mobile app. Per OpenAI's Help Center, the permission prompt only triggers the first time you create a task on the mobile device itself.
Is there a way to check if ChatGPT itself is having an outage affecting tasks? Yes, check status.openai.com. If multiple users report the same symptom the same day, an OpenAI-side incident is more likely than a setting on your end.
Keep your automations honest (and your inbox smart)
A silent automation is worse than no automation at all. At least when nothing runs, you know to check. Match your symptom to the table above, and if the job has outgrown ChatGPT Tasks, move it to a tool built for the job instead of patching around it.
If you want more of this, honest breakdowns of automation tools including the “this isn't the right tool for that” verdicts, subscribe to our newsletter. No hype, no affiliate cheerleading.