Scalr incident
Runs Failing with "Self-hosted agent pool assignment is required by policy."
Scalr experienced a notice incident on August 25, 2026 affecting Scalr Platform, lasting 1h 7m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 25, 2026, 12:23 PM UTC
Customers who force agent pool assignment on workspaces are seeing the error "Self-hosted agent pool assignment is required by policy." even when an agent is assigned. We are rolling back the code that caused this issue now.
- monitoring Aug 25, 2026, 01:11 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 25, 2026, 01:31 PM UTC
This incident has been resolved.
- postmortem Aug 25, 2026, 07:09 PM UTC
**Root cause** A regression in a release deployed the morning of 2026-08-25 caused the run policy engine to incorrectly flag self-hosted agent pool assignments as non-compliant, triggering the error above even for correctly configured workspaces. **Resolution** The release was rolled back, restoring normal behavior. No customer action is required. **Preventive measures** We are adding regression test coverage for this specific scenario \(self-hosted agent enforcement combined with valid pool assignment\) to prevent recurrence, and reviewing our release validation process for this code path. We apologize for the disruption this caused to your pipelines.