We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The deprecated [special tasks]clock-trigger configuration appears to cause execution retry delays to be skipped.
[special tasks]clock-trigger
execution retry delays
With the following workflow the execution retry delays skipped, but if you swap out the clock-trigger for an xtrigger, then it behaves correctly:
clock-trigger
[scheduling] initial cycle point = previous(T00) final cycle point = PT1S # [[xtriggers]] # clock = wall_clock(PT1H) [[special tasks]] clock-trigger = foo(PT1H) [[graph]] T00 = """ foo # @clock => foo """ [runtime] [[foo]] execution retry delays = PT30S script = false
The text was updated successfully, but these errors were encountered:
When you say skipped, I have found it to do the specified retries, but immediately instead of waiting for the given period
Sorry, something went wrong.
I think that's probably what I meant.
MetRonnie
Successfully merging a pull request may close this issue.
The deprecated
[special tasks]clock-trigger
configuration appears to causeexecution retry delays
to be skipped.With the following workflow the
execution retry delays
skipped, but if you swap out theclock-trigger
for an xtrigger, then it behaves correctly:The text was updated successfully, but these errors were encountered: