Claude Code scheduled task never fired? Compare with a Sume cron run

First update Claude Code, since 2.1.292 (Oct 6) fixed scheduled tasks that were created after /resume, /branch or /clear and never fired. Then separate the two clocks: a Claude Code task fires from your Claude session, while a Sume schedule is a saved automation that runs from a cron expression on Sume's side.

The changelog (read 2026-10-07) lists three related fixes in the past week, and each needs its own check.

The Claude Code fixes

The changelog lists, for 2.1.292, scheduled tasks created after /resume, /branch or /clear that never fired. For 2.1.288 (Oct 2), scheduled tasks lost in cloud sessions. For 2.1.287 (Oct 1), tasks set in the foreground that never fired after a hand-off.

If your missing run falls in one of those cases, the fix is an upgrade. Check the version first.

How a Sume schedule differs

A Sume schedule has instructions, a model, a cron expression with an IANA timezone, and a spend cap. When it fires it runs the agent in a fresh thread and returns a run receipt. It does not need your laptop or a Claude session to be open.

You create schedules in the Agents dashboard, or ask the agent in chat. The Developer API can list and read them and start runs, but it cannot create or edit them.

Reading a Sume run that did not execute

Sume run statuses are queued, processing, completed, failed, canceled and skipped. A skip because an earlier run is still going shows previous_run_active with a retry-later next action. This follows the on_active_run setting, which is skip or reject.

So "it never fired" has a clear answer on Sume's side: list the runs for that schedule and read the status, rather than guessing.

A short triage list

Check the Claude Code version. Check how the task was created, since the fix concerns tasks made after /resume, /branch or /clear. Check whether the task was in a cloud session. Then look at Sume: list the schedule's runs and read the newest status. If Sume shows a completed run and Claude shows nothing, the media exists and you only need to read the receipt.

If Sume shows skipped, an earlier run was still going; fix the cadence or the overlap setting, not the client.

Split the work between the two

Use Claude Code scheduling for jobs that need your repo and tools. Use a Sume schedule for media that must happen on time whether or not your machine is on. If a Claude task needs the result of a Sume run, have it read the receipt, not start a duplicate. Keep one source of truth for the cadence.

Remember that a Sume schedule has a default generation cap of $1.00, so a run that appears to under-deliver may simply have reached the cap; read the receipt before raising it.