-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
97028: Update DR SavedClaim status updater jobs to skip records in a final status #19498
Conversation
Generated by 🚫 Danger |
…ts-api into 97028-DR-status-job-updates
66463b6
to
9984270
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good! I have a draft PR that pulls the updater job specs into shared examples, so if that gets merged first you will have a little merge conflict fun to deal with, but shouldn't be too bad!
Backend-review-group approval confirmed. |
Summary
This change updates the DR SavedClaim status updater job to skip API requests for individual records in final statuses (i.e.
complete
,vbms
,error
, and if a record is not foundDR_404
).Related issue(s)
department-of-veterans-affairs/va.gov-team#97028
Testing done
Statuses were fetched every time before unless a claim plus the associated evidence was considered successful. This reduces redundant API calls since a large number of these calls are unnecessary as the status typically does not change after a record is in one of the final statuses.
What areas of the site does it impact?
This affects the DR SavedClaim status updater sidekiq jobs.
Acceptance criteria