[Enhancement] - Issue-1710/Add Retries to Case Loading #1803
Conversation
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
wittejm
reviewed
Jan 22, 2026
Contributor
wittejm
left a comment
wittejm
left a comment
There was a problem hiding this comment.
Thanks for the PR! You said
I believe the API endpoint we set up is restricted to the main site only?
Not clear what you're referring to. Are you able to run the stack locally and do you have login credentials?
Contributor
Author
Yeah, was able to get the stack running locally and was able to login with the creds Michael gave me. 👍 I'll send you a DM of the error. |
wittejm
approved these changes
Jan 23, 2026
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.
As mentioned in issue #1710, there has been an issue where a case is on record but requires multiple attempts/refreshes on the API endpoint before the case details can be accessed.
This PR attempts to resolve this with a minor tweak to the
getfunction for loading cases from the courts. In the fix, a retry loop is introduced with 3 retries at 2-second backoff intervals before erroring out. This would take the load off the user needing to manually refresh or open the case file link several times, the loop will attempt this for them.In theory, this should solve the issue mentioned in issue #1710, but I couldn't test the loop locally. I believe the API endpoint we set up is restricted to the main site only?
However, depending on how flaky the connection with the court servers is, we could adjust the backoff time to 3 seconds between attempts from 2 seconds.