Repository navigation
Fix the live matrix's existing-case path against staging - #311
Merged
Merged
Conversation
Case lookup writes its guided court answer into #court rather than Confirm information's #court_code, and an existing case's People screen asks which recorded party the filing is for instead of the filer's role. Both stopped the existing-case scenario on staging after #304-#310. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Change
The live filing matrix (
RUN_FILING_MATRIX=1) stopped on its existing-case scenario when run against staging after #304–#310:#court, butselectGuidedCourtwaited for Confirm information's#court_code. The helper now takes the select's ID.Test-only; no app code changes.
Validation
Against
litefile-staging.fly.devon release v83 (mergedmain, 36c81bc):massachusetts-stageandvermont-stageEFM services answered 503 Service Unavailable, both directly and through the EFSP proxy.🤖 Generated with Claude Code