Datto incident

Autotask PSA - LR, UKLR, UK01, UK02, UK03, EU1, DE1 - Intermittent Error Messages

Minor Resolved View vendor source →

Datto experienced a minor incident on June 4, 2026 affecting Limited Release and UK Limited Release (United Kingdom) and 1 more component, lasting 6h 5m. The incident has been resolved; the full update timeline is below.

Started
Jun 04, 2026, 07:55 AM UTC
Resolved
Jun 04, 2026, 02:00 PM UTC
Duration
6h 5m
Detected by Pingoru
Jun 04, 2026, 07:55 AM UTC

Affected components

Limited ReleaseUK Limited Release (United Kingdom)UK (United Kingdom)UK 2 (United Kingdom)UK03 (United Kingdom)EU1 (English Europe and Asia)German (Deutsch)

Update timeline

  1. investigating Jun 04, 2026, 07:55 AM UTC

    We are aware of a problem where error messages are being experienced when navigating the Autotask PSA UI. The Kaseya R&D Team is actively investigating this behaviour. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified Jun 04, 2026, 10:04 AM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jun 04, 2026, 10:35 AM UTC

    Thank you for your patience while we continue to work on a fix for this issue. A workaround to prevent the error messages has been confirmed. If you navigate within Autotask to the top right-hand corner: My Account > My Settings > Reset Settings Please note that when applying this change, many of your current settings will be reset. This includes certain column choosers, notification template defaults, search grid default criteria, and default checkbox/radio button selections.

  4. monitoring Jun 04, 2026, 01:12 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jun 04, 2026, 02:00 PM UTC

    This incident has been resolved.

  6. postmortem Jul 02, 2026, 01:55 PM UTC

    # Summary: Between 2026-06-04 05:30 UTC and 2026-06-04 12:00 UTC, some customers experienced intermittent error messages when navigating the Autotask PSA user interface, which impacted their ability to view certain tickets. # Root Cause: A recent product release \(version 2026.3\) introduced a defect that caused an error to appear under specific ticket grid and data configurations. # Incident Timeline: * Identified: 2026-06-04 07:00 UTC * Public Notification to the Status Page: 2026-06-04 07:55 UTC * Workaround posted to the Status Page: 2026-06-04 10:35 UTC * Resolved: 2026-06-04 13:00 UTC # Preventative Measures: To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps: * **Enhancements to Software Delivery Practices:** * Expand regression test coverage for ticket-related workflows impacted by code changes * Introduce additional validation checks for optional or missing data scenarios prior to release * Require clearer developer and QA documentation of tested scenarios for all bug fixes * **Enhancements to Quality Assurance:** * Add targeted test cases for edge conditions involving incomplete or non-standard ticket configurations * Improve automated test coverage around UI data validation paths