enabled: false Silently Disabled Claude Code Scheduled Tasks

Описание и применение

Автоматизированные задачи Claude Code могут остановиться тремя способами: не запуститься, умереть в середине выполнения или быть отключены. Для надёжного мониторинга автор проверяет наличие артефактов в git, автоматически включает отключённые слоты, ограничивает восстановление до двух статей за запуск и меняет порядок задач, чтобы сначала собирать данные о трафике.

Задача

Claude Code scheduled tasks can stop in three ways—never start, die mid‑run, or have the slot disabled—leading to missed content and unreliable monitoring.

Результат

The new monitoring and task management approach reduced missed articles, eliminated false failure alerts, and ensured that disabled slots are re‑enabled daily.

Рабочий процесс

• 1. At each slot start, count articles already published that day and slots passed.
• 2. If a slot is disabled (enabled:false), flip it to true and log the action.
• 3. For article slots, first pull traffic numbers, then write the article; for stocking slots, write separate heartbeat files.
• 4. Limit catch‑up to two articles per run to avoid extended runtimes.
• 5. Monitor artifact creation in git; if missing, treat slot as failed.
• 6. Adjust command syntax to use single commands with git -C and npm --prefix to avoid permission prompts.
• 7. Widen artifact detection window to 180 minutes based on measured median times.

Доказательства

Running Claude Code's scheduled tasks unattended, we found they stop three different ways.

Источник

We capped the catch‑up at 2 articles per run, for three reasons: ... The longer one run takes, the higher the chance it dies mid‑run

Источник

Now, at the start of the first slot each day, we list every scheduled task. If a writing slot is set to false, we flip it back to true and add one line to the report

Источник

We widened the window to 180 minutes and the false alarms went away.

Источник