fix(engine): defensive cleanup for orphaned scheduled actions#783
Merged
chubes4 merged 1 commit intoExtra-Chill:mainfrom Mar 11, 2026
Merged
Conversation
Adds a guard in the datamachine_run_flow_now action hook that checks if the flow exists before attempting execution. If the flow was deleted without cleaning up its Action Scheduler actions (historical cruft or edge cases), the orphaned actions are automatically cancelled with a warning log entry. This prevents recurring 'Flow not found' errors every time an orphaned scheduled action fires. - Adds datamachine_flow_exists() helper for lightweight flow lookup - Updates datamachine_run_flow_now hook with defensive early-return - Logs cleanup events for observability
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
2 participants
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.
Problem
Flows deleted without proper Action Scheduler cleanup leave behind orphaned scheduled actions that fire repeatedly, causing "Flow not found" errors every 6 hours.
Solution
Adds a defensive guard in the
datamachine_run_flow_nowaction hook that:Changes
datamachine_flow_exists()helper for lightweight flow lookupdatamachine_run_flow_nowhook with defensive early-returnTesting
Fixes recurring "Flow not found" errors from historical cruft or edge case deletions.