Update 5:41 pm:  We are turning real time calculations (refund monitor and AGI monitor) back on

Update 5:30 pm:  We are bringing the rest of the servers online as we are seeing response times in the normal operational range.  We are continuing to monitor the changes to the system as we bring everything back online.

Update 5:04 pm:  for those sites coming on board and those who are following the blog post, we are continuing to work on the errors and slow response times.  We currently cannot give you a resolution time.

Update 4:46 pm:  We have duplicated the errors you are seeing in the application and are working to determine the cause of the errors and slowness.

Update 4:24 pm:  The sytems are still booting up so you will experience slowness until all systems get online.  You may also receive a an unexpected error because of the lengthy wait time

Update 4:14 pm:  We are preparing to bring the first 18 servers out of standby

Update 3:45 pm: We will soon be placing the site in maintenance for a period of 30-45 minutes to allow our engineers to perform more granular investigation. We apologize for the inconvenience this continues to cause.

Update 2:37 pm:  We are turning off “Real time” calculation (Refund monitor) to do some analysis

Update 2:34pm:  We are seeing some lag time internally that we are currently investigating.

Update 2:13 pm:  The web services have completed.  We are seeing significantly less lag time going between pages.  We are continuing to monitor.

Update 1:46 pm:  We are doing a rolling reboot of our webservices that take the connections between you and our other services.  We will update the blog when this process has been completed.

Update 1:42 pm:  If you stuck opening a return, click on the Personal Information Section in the left navigation bar (if it is visible to you).  This will break the cycle and allow you to work through entering data.  The return will be slow calculating through pages.

Update 1:31 pm:  We are continuing to determine what is causing the slowness between pages.  

Update 1:18 pm:  We know it is taking a significantly slower than usual time for some users to open existing returns and move between entering the SSN and the personal information page.  We are currently looking to see the cause and find a solution.

1We are receiving information from sites that there is a sudden slowdown starting returns and going between pages.  We are currently looking into this.

12:28pm ET

The deployment has been applied to all servers. At this time, impacted sites with Rhode Island returns should now be able to access Summary/Print, see the Refund Generator with Results, and access E-file. Please let us know if you experience additional issues.

11:30am ET

The deployment for the fix is still occurring. As noted in the 10:47am ET update, deployment across all servers will take an hour or two before complete.

10:47am ET

The fix is currently being deployed at this time. For impacted sites with Rhode Island returns, calculations inside the returns should start to appear as the deployment continues. This will continue over the next couple of hours as the deployment continues across all servers.

10:37am ET

We anticipate having this resolved soon.

10:17am ET

Testing is still occurring in our pre-production levels before deploying live.

10:01am ET

The fix is currently being tested in our pre-production levels.

9:49am ET

Our engineers believe the issue has been identified and are working to resolve.

9:35am ET

Issue 2699 has been opened to investigate sporadic reports of the calc breaking in a return when a Rhode Island state return is added. We are looking into this.

The five questions that we assign on behalf of the IRS are not currently available in the returns.  We are working to re-establish them.

2/6/2019

Arizona Department of Revenue sent the below message late yesterday evening. AZ acknowledgements should begin populating at your sites as they work through their backlog.

“Thank you all for your patience. The issue with BR901 has been resolved. Please resume all activity (sending submissions, calling acknowledgements, etc.). Let us know if you additional questions.”

**Arizona also sent erroneous Reject Code 901’s. If your site had any AZ return rejected for Reject Code 901, AZ has stated these can be resubmitted.

2/5/2019

Software vendors have received the below messaging from the Arizona Department of Revenue.

“Please be advised that Arizona has temporarily suspended receiving submissions from the IRS. We will notify you when we start accepting returns.”

Arizona returns can still be transmitted to TaxSlayer as normal, just be advised there will be a delay in receiving acknowledgements.

2/6/2019

Ohio sent the below messaging to software vendors this morning.

“Ohio is currently in the processing of re-sending out all acknowledgements which were not received.  We are estimating that all acknowledgments will be re-sent out and received over the next several business days.  A follow-up email will be sent when all acknowledgements are showing received in our system.  The problem appears to be an intermittent problem, and we are still researching the issue to ensure this does not happen for future submissions.”

2/4/2019

Ohio sent a message to all software developers that they are aware of an issue that is isolated to acknowledgements only.  All submissions were processed according to the standard Ohio processing and rejection rules.  They are aware of the error and are currently researching the cause and will notify software vendors when there is a resolution.

1/31/2019 – 7:46am ET

Issue 2487 has been resolved. The requested payment date when “E-file: Direct Debit” for Federal return now correctly displays on the Client Listing Form Summary and included in the transmission.

We have opened Issue 2487, actively being worked, to correct an issue where the date of filing a Federal return is being sent when “E-file: Direct Debit” is selected with a future debit date. For example, if a taxpayer has a balance due Federal return and is filed on 1/30/2019 with a requested direct debit date of 4/15/2019, the filing date of 1/30/2019 is being sent as the debit date.

We anticipate having this resolved this week at the earliest.

1/30/19 – Impacted IN returns with Reject Code 60014 can be resubmitted as “State Only” if Federal previously accepted.

If your site(s) has any returns with Indiana Reject Code 60014, hold these state returns until this blog post has been marked as “Resolved” and “Send State Only” has been turned on.

Indiana Reject Code 60014 – “Schema not found with StateSchemaVersion: INIndividual2018V1.3, and ReturnType:IT-40”

1/30/2019 – Impacted returns can now be resubmitted for processing.

Problem:

Reject Code: R0000-019 | Category: Data Mismatch | Severity: Reject

Solution:

We will be issuing a software update on January 29th to resolve this.  Please hold returns with this reject until further notice.