Skip to content

Conversation

@google-labs-jules
Copy link
Contributor

Implemented a fix in src/runner/workflow-state.ts to check if all items of a foreach step are successful during state restoration. If so, the step status is upgraded to SUCCESS in memory, overriding any RUNNING or PENDING status from the database. This ensures workflows can resume correctly from such states. Added a verification test.


PR created automatically by Jules for task 5413483979200927558 started by @mhingston

Prioritize derived status from child items over stored parent status in `WorkflowState.restore`.
If all items in a foreach step are successful, the step is treated as SUCCESS even if the DB record says RUNNING or PENDING. This prevents unnecessary re-execution or stalls when resuming workflows that crashed after completing all iterations but before updating the parent step.

Added a regression test `tests/runner/foreach_restore.test.ts`.
@google-labs-jules
Copy link
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Prioritize derived status from child items over stored parent status in `WorkflowState.restore`.
If all items in a foreach step are successful, the step is treated as SUCCESS even if the DB record says RUNNING or PENDING. This prevents unnecessary re-execution or stalls when resuming workflows that crashed after completing all iterations but before updating the parent step.

Added a regression test `tests/runner/foreach_restore.test.ts`.
@mhingston
Copy link
Owner

Fix the linting Jules

@google-labs-jules
Copy link
Contributor Author

Fix the linting Jules

Linting issues fixed.

Prioritize derived status from child items over stored parent status in `WorkflowState.restore`.
If all items in a foreach step are successful, the step is treated as SUCCESS even if the DB record says RUNNING or PENDING. This prevents unnecessary re-execution or stalls when resuming workflows that crashed after completing all iterations but before updating the parent step.

Added a regression test `tests/runner/foreach_restore.test.ts`.
@mhingston mhingston marked this pull request as ready for review January 10, 2026 11:52
@mhingston mhingston merged commit 830869e into main Jan 10, 2026
1 check passed
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