scalr.io Status

Postmortem: 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.

Resolved: This incident has been resolved.

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

Identified: 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.

Resolved: This incident has been resolved.

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

Investigating: The docs site is currently down. We are working with the vendor to understand what the issue is.