Feature flags that were updated during 09:14:39 PM UTC and 11:39:44 PM UTC were experiencing delays to propagation.

Incident Report for Harness

Postmortem

Summary

On February 26, 2026, feature flags updated between 09:14:39 PM UTC and 11:39:44 PM UTC experienced delays in propagation. Feature flag evaluation through SDKs continued to function normally during this time. This was part of the planned maintenance activity

Impact

  • Feature flag updates made between 09:14:39 PM UTC and 11:39:44 PM UTC experienced delayed propagation.
  • The delay affected the time it took for flag configuration changes to appear across the system.
  • Feature flag evaluation through SDKs continued to operate normally, and applications relying on flag evaluation were not impacted.
  • Once the issue was resolved, all pending propagations began processing and the system returned to normal behavior.

Root Cause

The issue was caused by a temporary delay in the internal propagation pipeline responsible for distributing feature flag configuration updates across the platform as we were in middle of the planned maintenance activity

During the affected window, propagation tasks accumulated in the processing pipeline, which delayed the distribution of updated flag configurations. This did not affect flag evaluation or SDK operations but delayed the visibility of configuration updates.

Remediation

Engineering teams resolved the issue by rolling back and restoring normal processing of the propagation pipeline and allowing the queued updates to be processed. All delayed updates from the affected time window have since propagated successfully.

Action Items

To prevent from such issues from happening again

  • Enhanced monitoring for propagation latency to detect delays earlier.
  • Improved alerting for propagation backlog thresholds.
  • Additional safeguards to ensure faster recovery if propagation queues accumulate.
Posted Mar 04, 2026 - 11:57 PST

Resolved

Feature flags that were updated on Feb 26, 2026 during 09:14:39 PM UTC and 11:39:44 PM UTC were experiencing delays to propagation. The issue has been resolved, and all propagations from that window are recovering. No customer action is required
Posted Feb 26, 2026 - 13:14 PST