Unfortunately, during QA, we discovered that the process to fix this will be more complicated than expected. Consequently, we need another day to work on this fix. As of now, we are hoping to deploy the solution tomorrow afternoon.
I can provide an update first thing tomorrow.
We are finishing up QA on the potential fix. I will provide an update within the next few hours as to whether this fix goes into production today or not.
Our current plan is to deploy the fix Monday afternoon to ensure we can monitor the fix immediately after deployment in case of issues. If anything changes I will provide an update Monday morning. Otherwise, I will provide an update Monday afternoon after the fix is deployed.
We are finishing up work on a potential fix for this issue. At this time we expect it to be ready first thing Monday morning. I will provide an update by the end of the day.
We are continuing to work on a fix for this issue. Reporting data has started to fall out of sync for a couple of customers on other sites as well. We are not seeing any report viewing errors.
We will have an update tomorrow morning.
After some additional investigation, it looks like the situation has improved. We made some updates yesterday, and it looks like reporting period filters are no longer causing errors, and at least for some of the affected clients, the case data has caught up to this morning.
Some environments are not experiencing any issues related to this incident, but the US SaaS and PG HX continue to see reporting data falling out of sync or syncing inconsistently, though they are no longer seeing errors. We will continue to investigate.
After a cross-team discussion, we are implementing a new solution. This solution will most likely not be finished until the end of the day, at which point I can provide an update.
We are continuing to investigate the issues with the remaining affected hubs. Unfortunately we will not have a solution by the end of the day. I will provide an update first thing in the morning.
Since the last message, the issue has resolved for more customers, thanks to the fix we implemented. However, there are still some customers that are impacted. Our developers are looking into this now. We should have an update in the next few hours.
It looks like the fix has resolved the issue for some customers but not others. We will continue to investigate and should have an additional update in about five or six hours.
We are continuing to work on a fix for this issue. We should have another update by the end of the day.
Some reporting views show delayed Action Management case data for programs, as well as errors when using certain filters. Recent case activity starting yesterday may not yet appear in these views, and case counts may not reflect the latest updates.
Please note that no case data has been lost, and Action Management case creation and assignment continues to function normally.
We are working on a potential solution we hope to deploy tomorrow. We will be able to provide an update in the next few hours.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with