Skip to content

docs(schedules): explain running claims and when a job shows interrupted - #54

Closed
mrgoonie wants to merge 1 commit into
devfrom
claude/dazzling-archimedes-98e26g
Closed

mrgoonie wants to merge 1 commit into
devfrom
claude/dazzling-archimedes-98e26g

Conversation

@mrgoonie

Copy link
Copy Markdown
Contributor

Summary

This updates the official docs for nextlevelbuilder/dewee#1510 in both en and vi (concepts/schedules-and-heartbeat). A running job holds a claim. The gateway executing the run extends that claim every 30 seconds. A run in progress on any instance therefore survives a scheduler restart or takeover. A job shows interrupted only after its claim goes 2 minutes without being extended, and the scheduler then schedules its next run.

This page should publish only after the gateway change in nextlevelbuilder/dewee#1510 ships.


Generated by Claude Code

Copy link
Copy Markdown
Contributor Author

I'm closing this as a duplicate of #57, which documents the same cron behavior in the same place. The gateway ships nextlevelbuilder/dewee#1534 for #1510, and nextlevelbuilder/dewee#1529 (the design this page described) is closed. #57 matches #1534:

  • a scheduled time that comes up during a run is skipped;
  • Lite interrupts a crashed run when the gateway starts again, while PostgreSQL waits about 2 minutes.

#57 also carries this PR's updated: date bump.


Generated by Claude Code

@mrgoonie mrgoonie closed this Oct 20, 2026
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.

2 participants