Detailed Analysis
A user on the Claude Max plan reports a complete loss of interactivity with the scheduled tasks feature inside the Claude desktop application for macOS, posting to the /r/ClaudeAI subreddit seeking confirmation of a wider issue. The problem manifests in two distinct ways: the "Run Now" button is grayed out and non-functional across all four of the user's scheduled tasks, and the Save button within the task edit menu is similarly disabled, preventing any modifications to task configurations. The user confirmed they are running the latest version of the Claude Mac app, are not connected to a VPN, and had already performed standard troubleshooting steps including quitting and restarting the application and logging out and back in — neither of which resolved the issue.
The reported symptoms point to a possible session or state management bug rather than a simple connectivity or account-tier problem. One notable variable is that the user had been simultaneously signed into Claude on a second Mac beginning the day prior, then subsequently logged out of that device. This raises the possibility of a session conflict or a stale authentication state that persists even after the secondary device is logged out, which the client-side application may not be properly resolving. Additionally, the user notes that the primary email triage task had not run earlier that day due to the laptop being offline — a departure from normal behavior in which the task typically executes upon the machine coming online. The combination of a missed scheduled run and the subsequent locking of UI controls suggests the application may have entered an inconsistent internal state tied to task execution history or session validation.
The issue is significant because scheduled tasks represent one of the more sophisticated automation features available to Claude Max subscribers, and disruptions to this functionality cut directly against the productivity use cases that justify the plan's premium pricing. Features like automated email triage are not incidental; they represent core workflows that users build around, meaning outages carry immediate, tangible consequences for daily productivity. The fact that all four tasks were simultaneously affected — rather than just one — further suggests the problem is systemic to the task scheduler's state rather than isolated to a specific task configuration.
This incident reflects a broader challenge facing AI companies as they push beyond conversational chat into persistent, agentic workflows that operate autonomously on users' behalf. Scheduled tasks, background agents, and automated pipelines introduce a new class of reliability expectations distinct from interactive sessions: whereas a failed chat response is immediately visible and recoverable, a silently failed or locked scheduled task may go unnoticed until a critical workflow has already been missed. Anthropic's expansion into these autonomous, time-sensitive features requires correspondingly robust state management, session synchronization across devices, and clear failure signaling — areas where even mature software products routinely encounter edge cases. The user's post asking "Anyone else?" signals that the reliability of these systems is becoming a focal point of community scrutiny as adoption of Claude's agentic capabilities matures.
Read original article →