When the API returns a 400 Bad Request response, multiple dialogue boxes are displayed to the user instead of a single, consolidated error message.

**Describe the bug in the current situation**
When the API returns a 400 Bad Request error, the system first displays an “Unable to Save Filing” message. After the user clicks OK, a second message, “Unable to Retrieve Filing,” is displayed.

Steps to reproduce the behavior:
1. Go to 'https://dev.bcregistry.gov.bc.ca/en-CA/'
2. Search for BC0888283
3. File a Correction for the IA
4. Make some changes hit on "File and Pay"
5. Notice the "Unable to Save Filing" click on OK
6. Now observe another pop-up with "Unable to Retrieve Filing" shows up..

**Screenshots/ Visual Reference/ Source**

[Private Zenhub Video](https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBN1JFQ3c9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--010397a588e0f0a8fdd87a9d2b1aebe8b5832cf4/Screen%20Recording%202025-09-03%20at%204.11.49%20PM.mov)

Start by reproducing the issue at https://dev.bcregistry.gov.bc.ca/en-CA/ with entity BC0888283, then follow the filing correction flow through “File and Pay” until the API returns 400. Trace the handling of the “Unable to Save Filing” and “Unable to Retrieve Filing” messages; done means one consolidated error dialog is shown instead of two.

Written by the indexing model from the issue text.