Additional logging and handling for missing schedule errors #406
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
- Hard to track error in integration where the ProcessPostcodeWorker can't affect the backoff service because it can't see the scheduler. Can't replicate on the console, so add a bit of logging and defaults so that Sentry isn't overwhelmed with this odd error.
KludgeKML
force-pushed
the
schedule-missing-logging
branch
from
f250fa6
to
fa4e5da
Compare
georges1996
approved these changes
May 22, 2024
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.
Example:
https://govuk.sentry.io/issues/5348616796/?environment=integration&project=6288896&referrer=project-issue-stream
Follow these steps if you are doing a Rails upgrade.