API-8244: SpecialIssueUpdater Background Job Error #7332
Merged
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
SlakrHakr
force-pushed
the
slakrhakr/API-8244
branch
from
d666189
to
7657cb2
Compare
jw81
previously approved these changes
Jul 1, 2021
hinzed1127
previously approved these changes
Jul 1, 2021
SlakrHakr
force-pushed
the
slakrhakr/API-8244
branch
2 times, most recently
from
d848f41
to
2e3c299
Compare
hinzed1127
previously approved these changes
Jul 2, 2021
hinzed1127
previously approved these changes
Jul 2, 2021
SlakrHakr
force-pushed
the
slakrhakr/API-8244
branch
from
76ccd47
to
1137144
Compare
SlakrHakr
force-pushed
the
slakrhakr/API-8244
branch
from
1137144
to
95e1535
Compare
SlakrHakr
force-pushed
the
slakrhakr/API-8244
branch
from
95e1535
to
cc98076
Compare
hinzed1127
approved these changes
Jul 6, 2021
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.
Description of change
Unexpected error was noticed in sentry with regards to our background job to update special issues for a claim submission.
This appears to be happening in the situation where the Veteran has more than one contention but none of them match the particular claims that was submitted.
Original issue(s)
https://vajira.max.gov/browse/API-8244
Things to know about this PR
No new tests are present because there was already an existing test for this exact situation. It was unfortunately already "passing" because it simply detected if an exception was raised (which causes the job to be queued back up).