Hotfix/26.10.1#11753
Merged
Merged
Conversation
update `schedule_migrate_usage_reports` to resume scheduling after its last success when encountering a connection error, instead of restarting from the beginning (it should have been this way already, the logic was there, oops)
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
2 participants
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.
Ticket
Purpose
avoid repeating/wasting work in osfmetrics 6to8 data migration
Changes
update
schedule_migrate_usage_reportsto resume scheduling after itslast success when encountering a connection error, instead of restarting
from the beginning
(it should have been this way already, the logic was there, oops)
Side Effects
QE Notes
CE Notes
Documentation