Insights Dashboard: Delayed Maestro Run Data

Final update

## Customer impact Between September 2, 2026 at 7:59 pm UTC and September 4, 2026 at 4:30 pm UTC, the Insights dashboard did not display Maestro process runs created after the start of the affected window. The underlying data was never lost. It was held safely in our staging layer and became visible once processing resumed. The United States, Singapore, India, Canada, Australia, Japan, and United Kingdom regions were affected, with the exact duration varying by region from approximately 24.6 hours to 44.5 hours. The European Union region hit the same failure but recovered on its own within about 45 minutes, as described under Response below. Element-level Maestro data continued to update normally throughout, so the dashboard remained usable and did not appear broken; what was affected was the count and listing of recent process runs. ## Root cause A data processing task that moves Maestro process-run records from our staging layer into the database serving the Insights dashboard stopped running. The cause was a deployment sequencing problem. Two related changes are delivered by two separate deployment pipelines: one adds a new field to the staging layer, the other updates the proce

1. Postmortem · Sep 17, 22:13 UTC
   ## Customer impact Between September 2, 2026 at 7:59 pm UTC and September 4, 2026 at 4:30 pm UTC, the Insights dashboard did not display Maestro process runs created after the start of the affected window. The underlying data was never lost. It was held safely in our staging layer and became visible once processing resumed. The United States, Singapore, India, Canada, Australia, Japan, and United Kingdom regions were affected, with the exact duration varying by region from approximately 24.6 hours to 44.5 hours. The European Union region hit the same failure but recovered on its own within about 45 minutes, as described under Response below. Element-level Maestro data continued to update normally throughout, so the dashboard remained usable and did not appear broken; what was affected was the count and listing of recent process runs. ## Root cause A data processing task that moves Maestro process-run records from our staging layer into the database serving the Insights dashboard stopped running. The cause was a deployment sequencing problem. Two related changes are delivered by two separate deployment pipelines: one adds a new field to the staging layer, the other updates the processing task that reads it. In production the second pipeline ran approximately two hours before the first. The updated task therefore referenced a field that did not exist yet, and it failed on each scheduled run. Our data platform automatically suspends a task after a number of consecutive failures,
2. Resolved · Sep 2, 20:00 UTC
   The Insights dashboard in Looker experienced an issue that prevented the latest Maestro runs, from appearing in the dashboard Impacted regions : US, SEA, IND, CA, AUE,JP ,UK Incident timeline Started: September 2, 2026 at 20:00:00 UTC Resolved: September 4, 2026 at 16:30:00 UTC The issue has been currently resolved, and the Insights dashboard is displaying the latest Maestro run data.