Skip to content

Stop exhausted schedules from dispatching - #339

Merged
mostlydev merged 1 commit into
masterfrom
issue-zero-next-fire-schedules
Jul 2, 2026
Merged

mostlydev merged 1 commit into
masterfrom
issue-zero-next-fire-schedules

Conversation

@mostlydev

Copy link
Copy Markdown
Owner

Summary

  • Treat cron schedules with no future fire time as exhausted instead of immediately due.
  • Keep exhausted schedules out of the dispatch loop and omit next_fire_at instead of serializing zero time.
  • Normalize persisted zero time pointers in schedule state so old bad state stops leaking as 0001 timestamps.

Tests

  • go test ./cmd/claw-api ./cmd/claw

@mostlydev
mostlydev merged commit 67a42b5 into master Jul 2, 2026
2 checks passed
@mostlydev
mostlydev deleted the issue-zero-next-fire-schedules branch July 2, 2026 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant