Automation degradation

Resolved

Started

Lasted 22h 50m

View official incident ↗

Updates

  1. Resolved

    We determined the issue was caused by a role used by the automation service losing required permissions following a configuration change. The issue was reported on May 15 at approximately 1:00 PM PT and resolved on May 16 at 11:50 AM PT. To help prevent similar incidents, we have improved our alerting and added audit logging for role and permission changes.

  2. Investigating

    On May 15, some automations stopped running which impacted scorer executions.