claude-code - 💡(How to fix) Fix Durable cron jobs fire across all open sessions, not scoped to the session that created them [1 comments, 2 participants]

TL;DR

Implement session-scoped durable cron jobs or add a session-pinning option to prevent unintended job execution across multiple sessions.

Guidance

• Identify the current implementation of durable cron jobs and how they are stored or referenced across sessions.
• Consider adding a session identifier to each job to track which session created it and ensure only that session can execute it.
• Explore adding a configuration option or parameter to allow users to pin a job to a specific session, if scoping by creation session is not feasible.
• Review the current job execution logic to determine how to prioritize or restrict job execution based on the session that created the job or is pinned to it.

Notes

The exact implementation details of the durable cron job system and session management are not provided, so the guidance is focused on general approaches to addressing the issue.

Recommendation

Apply workaround: Implement session-scoped durable cron jobs or add a session-pinning option, as this directly addresses the reported issue and provides users with control over job execution across multiple sessions.