Datto incident
Autotask PSA - UK02 - Workflow Rule Delay and Latency
Datto experienced a minor incident on July 3, 2026 affecting UK 2 (United Kingdom), lasting 1h 49m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 03, 2026, 01:58 PM UTC
We are aware of an issue affecting Autotask users hosted in the UK02 zone, resulting in increased latency and delays in workflow rule processing. The Kaseya R&D Team is actively investigating this issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified Jul 03, 2026, 03:05 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 03, 2026, 03:18 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 03, 2026, 03:47 PM UTC
This incident has been resolved.
- postmortem Aug 25, 2026, 03:20 PM UTC
# Summary: Between 2026-07-03 11:41 UTC and 2026-07-03 15:09 UTC, some Autotask PSA customers hosted in the UK02 region experienced intermittent application performance degradation. Impacted customers may have encountered slow or unresponsive GUI behavior, widget timeout errors, and delays in workflow rule processing while queued workflow events were processed. # Root Cause: An intermittent hardware failure within the infrastructure supporting the UK02 environment caused unexpected database restarts. As a result, some application services experienced disrupted database connectivity, leading to intermittent application performance degradation and workflow processing delays until recovery actions were completed. ## Incident Timeline: * Identified: 2026-07-03 11:41 UTC * Public Notification: 2026-07-03 13:58 UTC * Resolved: 2026-07-03 15:09 UTC # Preventative Measures: To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. ### Enhancements to Infrastructure Resiliency * Review storage path failover configurations to improve resilience during intermittent connectivity events within redundant infrastructure paths. * Evaluate additional infrastructure resiliency improvements that may enhance automatic recovery during hardware connectivity failures. ### Enhancements to Application Resiliency * Improve application resilience to database connectivity interruptions to reduce service impact during infrastructure failover or recovery events. * Enhance automated recovery mechanisms so application services can restore normal operation more quickly following unexpected database disruptions. ### Enhancements to Incident Management and Response * Reinforce established incident response procedures across operational teams to ensure recovery actions are executed consistently and efficiently during similar events. * Provide additional cross-functional training to strengthen shared understanding of application and database interactions, enabling faster diagnosis and restoration of service.