fix: Increased time of delay for each retry of queued message (Provision) #595
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.
AB#44549
Description of work:
Because there have been some requests that have timed out when running its natural cause and there are not obvious exceptions we will try to increase the amount of time we delay the retry. We increase from 10 seconds * retryCount to 30 seconds * retryCount. This means that we will wait around 4 minutes before retrying the last time (fourth time).
NB! The initial code did prepare scheduledTime to be increased 10 seconds for each retry, but the value was never assigned to retryMessage. We will still increase the delay to be 30 seconds for each try.
Testing:
The function could be tested with natural processing of a request going through all the stages (create a new request, approve that request and then check that the request are beeing processed in provision). It is only when the provision-stage fails that we may experience the fix.
Checklist:
Considered updating specification / documentationConsidered security