Harness incident

Scheduled change request delayed for a subset of flags

Minor Resolved View vendor source →
Started
May 02, 2026, 12:01 AM UTC
Resolved
Apr 28, 2026, 05:21 PM UTC
Duration
Detected by Pingoru
May 02, 2026, 12:01 AM UTC

Update timeline

  1. resolved May 02, 2026, 12:01 AM UTC

    Between April 28 and May 1, 2026, a subset of scheduled change requests failed to execute at their scheduled times. The issue was introduced by a production deployment on April 28 and fixed with a new deployment on May 1. All affected scheduled jobs that had not been manually withdrawn by customers have since been executed successfully.

Looking to track Harness downtime and outages?

Pingoru polls Harness's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Harness reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Harness alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Harness for free

5 free monitors · No credit card required