Repository navigation
Add scheduled execution and persistent run history - #19
Merged
Merged
Conversation
nicosuave
marked this pull request as ready for review
September 8, 2026 01:50
nicosuave
force-pushed
the
scheduled-execution
branch
from
September 8, 2026 02:30
892c1fd to
0befde5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add interval and cron schedules for canvases and scripts using native alarms, with timezone selection, pause/resume, and run-now controls. Scheduled execution uses the latest validated revision and records each occurrence atomically.
Run history lives in supervisor SQLite and includes revision, trigger, status, and duration. Script logs correlate with runs and redact secrets. Canvas console capture and historical replay are explicitly outside this change.