{
  "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-24T11:07:10.141Z"
  },
  "data": {
    "id": "incident_statuspage_harness_q8vt26b0rxmn",
    "slug": "harness-scheduled-change-request-delayed-for-a-subset-of-flags-2026-05-01",
    "title": "Scheduled change request delayed for a subset of flags",
    "summary": "Scheduled change request delayed for a subset of flags",
    "status": "resolved",
    "severity": "minor",
    "startedAt": "2026-05-02T00:01:28.725+00:00",
    "updatedAt": "2026-05-06T04:02:51.657+00:00",
    "resolvedAt": "2026-04-28T17:21:00+00:00",
    "provider": {
      "slug": "harness",
      "name": "Harness"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/harness-scheduled-change-request-delayed-for-a-subset-of-flags-2026-05-01",
      "api": "/api/v1/incidents/harness-scheduled-change-request-delayed-for-a-subset-of-flags-2026-05-01",
      "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-24T11:00:50.68+00:00",
      "officialUrl": "https://status.harness.io",
      "statusPageUrl": "https://status.harness.io"
    },
    "updates": [
      {
        "id": "update_statuspage_harness_q8vt26b0rxmn_0d6rc6nf4lrv",
        "status": "resolved",
        "body": "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.",
        "createdAt": "2026-05-02T00:01:28.785+00:00"
      },
      {
        "id": "update_statuspage_harness_q8vt26b0rxmn_nfx3kwdfyhkm",
        "status": "resolved",
        "body": "## Summary\n\nBetween 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 service update on April 28 and resolved on May 1. All affected scheduled jobs that had not been manually withdrawn by customers have since been executed successfully.\n\n## Root Cause\n\nA service update exposed a latent bug in the path that retrieves applicable governance policies for a change request. This caused scheduled change request execution to fail, leaving affected change requests stuck in their scheduled state with no automatic retry.\n\n## Impact\n\n* Scheduled change request execution failed silently for a subset of flags on affected accounts\n* Affected change requests were not applied at their scheduled time; they remained visible as scheduled in the UI\n* SDKs and runtime flag evaluation were not impacted\n* No data loss occurred; all backlogged jobs have since been processed\n\n## Timeline\n\n| Time \\(UTC\\) | Event |\n| --- | --- |\n| Apr 28, 18:21 | Production deployment introduced the regression |\n| Apr 28, 20:31 | First scheduled change request execution fails |\n| May 1, 08:35 | First customer report received |\n| May 1, 09:43 | Escalated to engineering |\n| May 1, 19:43 | Fix deployed to production |\n| May 1, 22:28 | All stuck scheduled jobs confirmed published |\n\n## Remediation\n\n* Deployed a forward fix addressing the underlying latent bug and adding additional protections\n* Reset scheduler tasks, allowing the scheduler to re-execute them; all have since been confirmed published\n\n## Action Items\n\n* Enhance test coverage for scheduled change request execution edge cases\n* Add alerting for scheduled changes that have not executed within a threshold of their scheduled time, enabling proactive detection ahead of customer reports",
        "createdAt": "2026-05-06T03:58:02.813+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}