CLAUDE LABJP
2.1.281 — Claude Code reached 2.1.281 on September 23. The gateway now understands the newer Claude Desktop policy keys, and Bedrock upstreams gain assume_role and a guardrail setting10/07 — The old spellings of the Claude Desktop and Cowork managed config keys stop being accepted at 12:00 PT on October 7, thirteen days from now529 — A report describes background subagents ending mid-task on a transient 529, leaving the parent to piece together what actually survivedNEW — Bracketing PDF input tokens by page count before you send the fileRORK — Rork added Claude Opus 5.5 to its model menu on September 22, so the same model landed in several tools within one weekUNIT — When you hand off a long job, committing after each unit of work means a crash costs you one step, not the whole run2.1.281 — Claude Code reached 2.1.281 on September 23. The gateway now understands the newer Claude Desktop policy keys, and Bedrock upstreams gain assume_role and a guardrail setting10/07 — The old spellings of the Claude Desktop and Cowork managed config keys stop being accepted at 12:00 PT on October 7, thirteen days from now529 — A report describes background subagents ending mid-task on a transient 529, leaving the parent to piece together what actually survivedNEW — Bracketing PDF input tokens by page count before you send the fileRORK — Rork added Claude Opus 5.5 to its model menu on September 22, so the same model landed in several tools within one weekUNIT — When you hand off a long job, committing after each unit of work means a crash costs you one step, not the whole run
Articles/Cowork
Cowork/2026-09-24Intermediate

Will Your Cowork Scheduled Task Still Run Next Saturday?

A definition that runs once and stops, two fire times packed into one task, a weekday that quietly emptied after an edit. Cowork schedules can go missing without leaving a single log line. Here is a working audit that compares what you defined with what you meant.

Cowork43Scheduled Tasks12cron4Operations20Troubleshooting17

Premium Article

One Saturday morning, a single output that should have been waiting for me simply was not there. No error notification. The task list showed a neat column of green "enabled" toggles.

The cause was a small edit I had made myself earlier that week. I had two tasks taking turns on weekend work for two sites, and I moved one of them onto the same day as the other because it looked tidier. After that, nothing covered Sunday at all.

Nothing was broken. The schedule was simply missing a piece. As an indie developer who keeps adding unattended jobs, this is the kind of gap that costs me the most time.

You cannot find a task that never ran by reading run logs

The first thing I'd like to say plainly: this kind of gap does not show up in run logs.

A failed task leaves a log. A late task leaves some trace. A task that never fired writes nothing at all. The more carefully you read the logs, the more convinced you become that everything is fine.

I have written before about counting runs from the outside to catch gaps after the fact, in Half of My Scheduled Runs Vanished Without a Single Error. That approach catches a gap the day after it happens.

This piece is about the step before that. Read the task definitions themselves, and find where they disagree with your intent before anything runs.

Three ways my schedules went missing

Looking back over the last few months, every gap I hit fell into one of three shapes.

ShapeHow it looked in the listWhat actually happened
One-off definitionEnabled, next run shownA task I meant to repeat showed "One-time:" in its schedule field, ran once, and then disabled itself
Two fire times in one taskEnabled, cron looked correctI wrote 30 4,16 * * * to classify wallpaper categories morning and evening; in my environment only one of the two fired
A weekday emptied by an editEverything enabledI moved one of two alternating tasks onto the other's day, and nothing was left to cover Sunday

The wallpaper category job now runs as two separate tasks, one for the morning slot and one for the evening slot. Giving each slot its own name means I can see at a glance when only one of them is moving.

What the three have in common is that the list looked healthy every time. The toggles were on. The cron strings had no typos. What was missing was the information about what I expected — and that lives nowhere in the task definitions.

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
You will be able to surface one-off definitions, double-slot crons, and uncovered weekdays in a few minutes, using a ledger and a short script instead of staring at the task list
You will be able to check which weekdays a cron edit is about to remove before you save it, so silent gaps are stopped at edit time rather than discovered on a missing Saturday
You will be able to leave a reason next to every disabled task, so that months later you can decide whether it is safe to turn back on without guessing
Secure payment via Stripe · Cancel anytime

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • Copy-paste ready implementation code
  • New advanced guides published daily
  • $5/mo or $15 for lifetime access
View Membership →

Related Articles

Cowork2026-07-11
Make Your Nightly MCP Connectors' Health Visible — A Lightweight Ledger for Solo Operators
You don't need Enterprise connector observability to see your MCP connectors' error rate and latency. Append one line per tool call, roll it up weekly, and let regressions ring a bell. A working health ledger for anyone running scheduled tasks solo.
Cowork2026-07-02
How Many Tasks Fire in the Same Minute — Flattening Cowork Scheduled-Task Collisions from Cron
When Cowork scheduled tasks bunch up at the same time and fight over shared resources, you can expand every cron expression into fire times, count collisions and true concurrency, and shave the peak with a greedy offset that never moves your premium slots. With working code and measured before/after numbers.
Cowork2026-06-25
My Unattended Task Was Overwriting the Previous Day's Log — the Container's date Was Returning UTC
A Cowork scheduled task that wrote date-stamped logs was silently overwriting the prior day's file. The culprit was the container's date returning UTC. Here is how I isolated it and the permanent fix: pin the timezone, append instead of overwrite, and detect the failure.
📚RECOMMENDED BOOKS
Build a Large Language Model (From Scratch)
Sebastian Raschka
LLM Dev
Prompt Engineering for LLMs
Berryman & Ziegler
Prompting
AI Engineering
Chip Huyen
AI Eng
* Contains affiliate links