fix: skip RetryWait for new tasks in scheduler (#459)#460
Merged
Conversation
The scheduler was applying RetryWait to all tasks, including brand-new ones with Retries=0. This caused every SendTransaction task to wait 5 minutes before being picked up, even though it had never been attempted. The fix checks Retries==0 to identify new tasks and picks them up immediately, only applying RetryWait to tasks that have actually failed and are being retried.
alanshaw
approved these changes
Mar 26, 2026
This file contains hidden or 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
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.
The scheduler was applying RetryWait to all tasks, including brand-new ones with Retries=0. This caused every SendTransaction task to wait 5 minutes before being picked up, even though it had never been attempted.
The fix checks Retries==0 to identify new tasks and picks them up immediately, only applying RetryWait to tasks that have actually failed and are being retried.
closes #459