-
Notifications
You must be signed in to change notification settings - Fork 15
feat: add whenFailed option for error handling after retries exhausted #575
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 01-05-add_condition_evaluation_in_start_ready_steps_and_dsl_support
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: c25ab9f The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
View your CI Pipeline Execution ↗ for commit c25ab9f
☁️ Nx Cloud last updated this comment at |
5e8c404 to
c68bf9c
Compare
ccaa5de to
46b2302
Compare
46b2302 to
c25ab9f
Compare
c68bf9c to
7372203
Compare

Add whenFailed option for error handling after retries are exhausted
This PR adds a new
whenFailedoption to control what happens when a task fails after all retry attempts are exhausted. The option supports three modes:fail(default): Marks the step and run as failed, stopping executionskip: Marks the step as skipped and continues the runskip-cascade: Marks the step as skipped and also skips all downstream dependent stepsImplementation details:
when_failedcolumn to thestepstable with appropriate constraintsfail_taskfunction to handle the different failure modeswhenFailedoption in the TypeScript DSLwhenFailedsettingThis feature provides more flexibility in error handling, allowing workflows to continue execution even when non-critical steps fail.