[BUG] Routine notifications: email channel silently fails, push works
Status Closed — not planned
Reported on v2.1.223
Maintainer reply None cached
Activity 6 comments · opened Aug 6, 2026 · closed Sep 14, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I have a scheduled Routine in Claude Code desktop on macOS with both "Push notification" and "Email" checked under Notifications. When the routine completes and calls the notification tool, the push notification arrives correctly, but no email is ever received — not even in spam. This happened consistently across multiple runs on the same day.
What Should Happen?
Both configured notification channels (push + email) should deliver when a routine run triggers a notification, since both are enabled in the routine's Notifications settings.
Error Messages/Logs
Steps to Reproduce
- Create a scheduled routine (recurring trigger, e.g. daily/weekdays at a set time).
- In the routine's Notifications tab, check both "Push notification" and "Email".
- Let the routine run on its schedule (or trigger it) so it reaches the point where it sends a completion notification.
- Push notification arrives on mobile/desktop as expected.
- Check the email inbox associated with the account, including spam/junk folders — no email arrives.
- Repeat across multiple separate runs on the same day — same result each time: push works, email never arrives.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.223 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
6 Comments
I am experiencing this myself as well, and very clearly have only Email checked as a delivery target. I get no notification at all. Interestingly, when viewing the "Sent notification" output from the most recent run of my Routine, it says
Mobile push requested.despite being configured otherwise.<img width="749" height="349" alt="Image" src="https://github.com/user-attachments/assets/3ae6e7c6-6de4-42c6-9461-0997d3bfaefc" />
<img width="294" height="112" alt="Image" src="https://github.com/user-attachments/assets/5af84d5b-b61f-48a7-99e4-e48f66edbd18" />
I have the same issue since ~1-2 weeks. No mobile or mail notifications at all. No mail or push at:
did also already the spam check, iOS re-pair, verification if claude code
/configmobile device for notifications has no warning. Within the scheduled tasks i see that the send notification action is fired and in routines those settings are also setClosing for now — inactive for too long. Please open a new issue if this is still relevant.
LOL seriously? Even Claude Desktop knows this is broken.
``
Note: The notification tool used to email/push this summary is currently erroring on every call (status: proactive rejected as invalid input, even when omitted or matching the tool's own schema) — this looks like an environment bug that will need attention outside this session, since it will block all future scheduled notifications until fixed.``<img width="879" height="845" alt="Image" src="https://github.com/user-attachments/assets/04c67b7f-3c86-4a11-a630-8754a34bc0be" />
Adding another data point to this — same symptom, still occurring.
Setup:
30 13 * * 1-5)Run in question:
<routine_summary>produced as the final resultPushNotificationtool (returned "Mobile push requested") even though Push is toggled off for this routine — suggesting the agent-side notification call and the platform-side channel routing aren't in sync, which may be related to why Email silently does nothing here.Same as the original report: no error, no log, nothing user-facing to indicate delivery failed. Given this is closed as "not planned" but the underlying behavior still reproduces cleanly, could this get another look? Happy to provide more detail if useful.
@dbechaux Sorry to say they already closed the ticket. They're not planning to fix it.