Scenario:  Getting Invalid_Scope error when trying to open an existing return or create a new return

We will be pushing a fix out at approximately 8:30 EST

10:45am ET: This has been resolved.

9:30am ET: We are currently aware and actively working an issue where FSA users with a rejected return (Federal or state) are unable to correct and resubmit their tax return(s). This has been reported as Issue 3636 and only impacts FSA and NOT TaxSlayer Pro Online. This post will be updated once the issue has been resolved which we expect to be tomorrow, January 28th.

11:55am ET – The API error has been resolved and access to returns has been restored.

11:20am ET – We are aware and actively looking into the issue where users are getting the “API Error Response” message when attempting to access returns in the Practice Lab. Updates will be provided as they become available.

Update:  This has been resolved

We are currently working to resolve the slowness you are experiencing when opening returns (all years).

Update 8:30 am:  All errors have been resolved.

Update 8:03 am:  Errors accessing Roles and Permissions and the client portal lists have been resolved

As we are preparing to move into the new season, our dev team is working on some infrastructure changes.  Currently, the following features are not working as expected:  The Client Portal List, Accessing Roles & Permissions and access the e-file section.  You will see the following when trying to access the e-file section and need to close the browser to exit the messaging:

11:25am ET: This has been resolved.

10/3/25 – 10:12am ET: We are aware and actively working an issue where sites are unable to load the e-file pages. Updates will be provided as they become available.

7/1 – This has been resolved.

We are aware that you are receiving an error when clicking Save & Exit return from inside the return and the e-file section.

Workaround:  Select “Your Office” from the left navigation bar until this has been resolved

5/20/25 – 5:00pm ET:

This is has been resolved.

5/20/25 – 3:30pm ET:

Our third party chat provider is currently experiencing an issue that has made chat temporarily unavailable. Please use e-mail or phone support at this time.