一片一片 3ebd4de993

fix(scheduler): isolate a malformed stored schedule from the poll batch (#7999) ...

remain from its review:

- `stored_next_run_at` caught the ValueErrors a dropped zone or a newer cron
  parser raises, but a stored `schedule_spec` that is JSON null, a list or a
  string fails on `.get` with AttributeError. The launch-failure handler
  recomputes the schedule, so that escaped `run_once`'s claimed-task loop and
  skipped the rest of the batch. Catch it too; the task is paused with the
  reason like the other unusable schedules.
- `run_once` dispatched its claimed batch with a bare loop, so any per-record
  raise in `dispatch_task` re-aborted the batch. Isolate each task's dispatch
  and keep claim-level store failures loud above the loop.

Tests: `test_scheduler_poll_batch_isolation.py` (non-object specs, end-to-end
pause, per-task isolation). Red on `91f20a7`, green at head.

Refs #7998

2026-11-09 20:25:32 +08:00

..

__init__.py

feat: add scheduled tasks MVP (#3898)

2026-07-04 21:51:57 +08:00

notification_delivery.py

feat(channels): generalize group notifications and add opt-in task/goal IM notices (#6903)

2026-10-15 10:30:55 +08:00

notification_text.py

fix(runtime): present outputs before a loop wrap-up and explain step-limit stops (#7588)

2026-10-27 10:34:34 +08:00

service.py

fix(scheduler): isolate a malformed stored schedule from the poll batch (#7999)

2026-11-09 20:25:32 +08:00