Update 11:00 pm EST The time out messages going between Summary/Print and e-file has been resolved
Update 9:45 pm EST We have received reports and duplicated in house getting a “time out oops” message going between Summary/Print and e-file
Update 8:05 pm EST The process of rolling out the changes has completed. We will be leaving the Forms Completed (on the left navigation panel when in a return) off for now. We are evaluating the code stream to see if we need to make any optimizations, as this is the primary area that was generating the errors today.
Update 7:10 pm EST We are seeing calculations being rendered. We are still pushing to all servers, which means you may hit a server where the change has not been made yet. This process to roll out the changes can take up to an hour
Update 7:00 pm EST: We have identified the issue with the calculations not rendering. We are making another deployment to resolve this.
Update 6:25 PM EST — We have brought the servers out of Maintenance mode, however, the calculations are not rendering. When you open the return and appear to be stuck on calculating, remember you can click on Basic Information to break the cycle. This allows you to input the data, but it will not render a calculation. We are not seeing the errors we were experiencing earlier. We are still working to resolve this for you.
Update 5:42 PM EST — We are putting the site in maintenance mode for approximately 20-30 minutes.
Update 10 5:37 PM EST — We know that the majority of you online are having challenges with the returns calculating. If you are stuck with the returns
Update 9 5:17 pm EST — We are continuing to work to resolve the errors and the slowness in calculations.
Update 8: 4:25 PM EST — We have turned off Forms Complete on the left navigation bar, as it seems to be generating the most errors. We are investigating why that code stream is generating errors.
Update 7: 4:15 PM EST — We have the code change deployed to the first set of servers. We are monitoring those now to determine the impact of the code change.
Update 6: 4:05 PM EST — We are in the process of rolling out a code change. We are doing this on a few servers at at time.
Update 5 3:58 PM — We have a code change in QA. Once it passes on our Pre Production system, we will begin rolling it out to each server.
Update 4: 3:15 PM — We are seeing some errors on the site again, but not as widespread as earlier.
Update 3: We are back up to approximately 7700 users on the site. If you are having problems accessing the site to login, close all instances of your browser and open a new one.
Update 2: We are aware that you are getting kicked out and not being able to connect. We are working to determine the cause.
Update: We are now seeing a decrease in errors being generated by the application. We will continue to monitor.
We have received reports of sites getting Unexpected Errors. We currently have our engineering team reviewing these errors. If this occurs, please log out and open a new instance of your browser.