{
  "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-23T10:40:51.787Z"
  },
  "data": {
    "id": "incident_statuspage_harness_mz8709jq2dqv",
    "slug": "harness-vercel-integration-for-fme-is-having-delays-to-synchronize-changes-2026-05-11",
    "title": "Vercel Integration for FME is having delays to synchronize changes",
    "summary": "Vercel Integration for FME is having delays to synchronize changes",
    "status": "resolved",
    "severity": "minor",
    "startedAt": "2026-05-11T22:42:28.493+00:00",
    "updatedAt": "2026-05-13T01:55:44.394+00:00",
    "resolvedAt": "2026-05-11T23:15:48.044+00:00",
    "provider": {
      "slug": "harness",
      "name": "Harness"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/harness-vercel-integration-for-fme-is-having-delays-to-synchronize-changes-2026-05-11",
      "api": "/api/v1/incidents/harness-vercel-integration-for-fme-is-having-delays-to-synchronize-changes-2026-05-11",
      "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-23T10:35:04.081+00:00",
      "officialUrl": "https://status.harness.io",
      "statusPageUrl": "https://status.harness.io"
    },
    "updates": [
      {
        "id": "update_statuspage_harness_mz8709jq2dqv_1r015ky0mpwv",
        "status": "investigating",
        "body": "We are currently investigating this issue.",
        "createdAt": "2026-05-11T22:42:28.597+00:00"
      },
      {
        "id": "update_statuspage_harness_mz8709jq2dqv_w9fw6hdkz3dn",
        "status": "monitoring",
        "body": "A fix has been implemented and we are monitoring the results.",
        "createdAt": "2026-05-11T22:42:53.235+00:00"
      },
      {
        "id": "update_statuspage_harness_mz8709jq2dqv_hw5n7mjl95xv",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2026-05-11T23:15:48.044+00:00"
      },
      {
        "id": "update_statuspage_harness_mz8709jq2dqv_xdyv6m75w6k6",
        "status": "resolved",
        "body": "### **Summary**\n\nOn May 7, 2026, customers using the Vercel integration experienced delays in synchronizing Feature Management & Experimentation \\(FME\\) changes to Vercel. The issue was caused by a dependency update in the integration service that prevented outbound synchronization requests from being authenticated correctly. The issue was resolved on May 11, 2026 through a service fix and validation of synchronization workflows.  \n\n### **Impact**\n\n* Customers using the Vercel integration experienced delays propagating FME changes to Vercel\n* Customers observed stale configuration data in Vercel after updating changes in FME\n* Other FME functionality remained operational\n* No data loss occurred\n\n### **Root Cause**\n\nA deployment to the `integrations-service-v2` service introduced dependency updates that removed a required AWS SDK component used during request signing and authentication for synchronization calls.\n\nAs a result, outbound requests from the FME integration service to the synchronization endpoint could not be authenticated correctly, causing synchronization operations to fail.\n\nThe issue was not immediately detected because:\n\n* Existing monitoring metrics did not have alerting configured\n* The failure mode did not surface as a critical application startup error\n* Integration-level automated test coverage for this synchronization workflow was insufficient\n\n### **Resolution**\n\nThe missing dependency was restored and the synchronization workflow was validated across affected integrations. Monitoring and validation checks confirmed successful synchronization behavior after deployment.\n\n### **Preventive Actions**\n\nTo prevent such issues from happening again, We are implementing the following improvements:\n\n* Enhance end-to-end integration tests for the Vercel synchronization workflow\n* Enhance our proactive alerts for synchronization failures and elevated error rates",
        "createdAt": "2026-05-13T01:53:56.155+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}