-
Notifications
You must be signed in to change notification settings - Fork 93
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
custom outputs: output specific retry delays #5652
Milestone
Comments
A good idea! |
Skimming through the
|
1 task
I've been wanting this functionality for a long time, so yes, please. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The optional outputs extension proposal opens up new opportunities for task outputs.
E.G. Here's an example which uses the new completion expression to tolerate a particular type of error:
In this example, the task
get_data
will still fail, but the failure will be tolerated (by optional outputs) because the completion condition permits failure for this case.For this example it would be reasonable for the user to want to configure retries differently for each case e.g:
:network_failure
->retry delays = PT5M
- retry every 5 mins until the network comes back:authentication_failure
->retry delays =
- no point retrying:data_not_ready
->retry delays = 1 * PT10M
- give it 10 mins, retry once, then give inTo support this we could consider something like:
The text was updated successfully, but these errors were encountered: