Legal API: HTTP 500 when trying to resume a COA correction
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Found in Dev:
1. login to BCROS as staff
2. open a business with a recent filing (eg, COA)
3. click down arrow beside COA filing and select "File a Correction"
4. enter the correction detail, legal name and check mark
5. enter an invalid Routing Slip Number (eg, 12345689)
6. click "File and Pay"
7. observe that Correction - Address Change filing is in Draft state
8. click View Details
9. observe that filing is "Payment Incomplete - This Routing Slip is not active"
10. click Resume button
11. observe "Unable to Resume Filing" dialog
12. observe console error:
13. observe 500 error in network tab:
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the BCROS correction flow with an invalid Routing Slip Number, then inspect the browser console and the failing network request when Resume is clicked. Trace the Legal API request and its error handling; done means resuming this inactive-routing-slip draft no longer produces an HTTP 500 or an unhandled Unable to Resume Filing failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, javascript, python
- Domain
- api, backend, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100