Retry scheduled process opn failure #38
Closed
Conversation
This file contains 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
pierredup
force-pushed
the
retry-scheduled-run
branch
from
c96f36d to
c6f9459
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When a scheduled process returns an error, it does not automatically get retried and only runs again on the next schedule. Other process types are automatically retried after a delay, so this tries to align with the same process to retry a failed scheduled run. The process will keep on retrying until maxErrors is reached (if it's set), and won't trigger another scheduled run while the process is retrying. After a successful run, the process will only execute again on the next schedule (I.E it won't try to run previous schedules that were missed during the retry period).