{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-07-23T08:06:16.261Z"
  },
  "data": {
    "id": "incident_statuspage_harness_jdldmbrldlk6",
    "slug": "harness-feature-flags-unable-to-update-2026-04-15",
    "title": "Feature Flags unable to update",
    "summary": "Feature Flags unable to update",
    "status": "resolved",
    "severity": "minor",
    "startedAt": "2026-04-15T23:55:37.466+00:00",
    "updatedAt": "2026-04-30T17:37:52.188+00:00",
    "resolvedAt": "2026-04-16T04:15:55+00:00",
    "provider": {
      "slug": "harness",
      "name": "Harness"
    },
    "affectedServices": [
      {
        "slug": "harness-feature-flags",
        "name": "Feature flags & FME"
      }
    ],
    "links": {
      "html": "/incidents/harness-feature-flags-unable-to-update-2026-04-15",
      "api": "/api/v1/incidents/harness-feature-flags-unable-to-update-2026-04-15",
      "providerHtml": "/providers/harness"
    },
    "impactSummary": "Harness reported a minor event for the affected tracked services.",
    "source": {
      "id": "source_harness_status",
      "kind": "official_api",
      "name": "Harness Status",
      "checkedAt": "2026-07-23T08:00:14.388+00:00",
      "officialUrl": "https://status.harness.io",
      "statusPageUrl": "https://status.harness.io"
    },
    "updates": [
      {
        "id": "update_statuspage_harness_jdldmbrldlk6_7n5z3h7x81ff",
        "status": "investigating",
        "body": "We are currently investigating this issue.",
        "createdAt": "2026-04-15T23:55:37.549+00:00"
      },
      {
        "id": "update_statuspage_harness_jdldmbrldlk6_ctw636p3lz77",
        "status": "investigating",
        "body": "We are continuing to investigate this issue.",
        "createdAt": "2026-04-16T00:01:57.089+00:00"
      },
      {
        "id": "update_statuspage_harness_jdldmbrldlk6_x4n3pl1tt66c",
        "status": "monitoring",
        "body": "A fix has been implemented and we are monitoring the results.",
        "createdAt": "2026-04-16T04:04:25.185+00:00"
      },
      {
        "id": "update_statuspage_harness_jdldmbrldlk6_m5psygsfkhrl",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2026-04-16T18:05:55.537+00:00"
      },
      {
        "id": "update_statuspage_harness_jdldmbrldlk6_2hp7cybhym9p",
        "status": "resolved",
        "body": "## **Summary**\n\nOn April 15, 2026, between approximately 23:21 UTC and 01:58 UTC, customers using Feature Flag  in the prod2 environment experienced delays in feature flag updates.\n\nFeature flag changes made via UI or API were successfully processed but were **not immediately reflected**, causing stale flag values to be served.\n\n## **Impact**\n\n* **Scope:** Customers on **prod2 environment only**\n* **Customer Impact:**\n\n    * Feature flag updates were **delayed or appeared ineffective**\n    * Applications continued serving **stale configurations**\n    \n* **Other Environments:** No impact to prod0, prod1, or other regions\n\n## **Root Cause**\n\nThe issue was caused by replication lag in the read replica database used for serving feature flag reads. A **long-running read query** on the replica blocked replication updates from the primary database. This caused a delay in propagating recent feature flag changes to read queries\n\n### **What triggered the issue**\n\n* A high-volume API usage pattern involving **large paginated queries on target data.** These queries became **resource-**intensive impacting the database.\n\n## **Mitigation**\n\n### **Immediate Actions**\n\n* Identified and **terminated long-running queries** on the replica\n* Replication resumed and flag updates began reflecting correctly\n\n## **Prevention & Next Steps**\n\nWe are continuing to strengthen reliability through:\n\n* We configured replica to **automatically cancel queries** that block replication beyond a threshold and tuned  **query timeouts** for heavy read operations\n* Improving **query efficiency and pagination strategies**\n* Enhancing **monitoring and alerting for replication lag**\n* Evaluating **database upgrades and scaling improvements**",
        "createdAt": "2026-04-30T17:34:11.302+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}