Skip to main content
Harness

Single Customer: IaCM pipeline executions failing intermittently in Prod 1

Degraded Lasted 4h 22m · started · Harness's page

Level
confirmed
Worst impact
Degraded
Components
Infrastructure as Code Management (IaCM)

What to do

  • Check whether you use Harness Infrastructure as Code Management (IaCM). Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 4h 22m it lasted.

    Anything that failed between 2026-10-06 11:58 UTC and 2026-10-06 16:21 UTC may need a replay.
  • Subscribe to Harness's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=harness works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Harness 5

  1. investigating

    We are currently investigating this issue.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. identified

    The issue has been identified and a fix is being implemented.

    provider

  4. resolved

    This incident has been resolved.

    provider

  5. postmortem

    ## Summary On **Tuesday, 6 October 2026**, IaCM pipelines that use the **OpenTofu plugin** in **Prod1** failed intermittently for a production accountAffected runs injected secrets successfully, then later steps timed out or failed authentication. The same pipeline often succeeded on retry, with no configuration change. Typical failing executions ran for about 90 minutes. Other Harness modules were not broadly impacted. We have no report of customer data loss. Pipelines that finished inside the token lifetime were unaffected by this defect. ## Root Cause The IaCM stages minted authentication tokens that expired after one hour. Policy checks later in a long run then rejected the token, so the step timed out or failed authentication. That one-hour lifetime was fixed. Runs of about 90 minutes crossed the one-hour mark, which is why the failures showed up on longer pipelines and often cleared on a shorter retry. A separate set of plan errors in the same account came from credential setup in the customer workspace and is outside this incident. ## Impact * **Product area:** IaCM pipelines using the IaCM plugins talking to OPA sdk. * **Customer experience:** intermittent timeouts and authentication failures after secret injection, on runs longer than about one hour. * **Environment:** Prod1, one production account * **Data:** No data loss reported. ‌ ## Remediation * **Immediate:** Opened a status page for the affected Prod1 account, and shipped an interim IaCM manager change for one class of the observed failures while the plugin fix was built. * **Permanent:** Shipped an OpenTofu plugin hotfix so token expiry is configurable. In production the lifetime was raised to about 6 hours, so a long pipeline does not outlive the token. The hotfix was validated in QA and deployed to Prod1. We apologise for the disruption caused. Please reach out to your Harness support contact if you have any further questions.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-dac282d5ef

Is Harness still down?

No, this incident was resolved 2026-10-06 16:21 UTC. For Harness's live state, see https://down.guide/harness.

How long did it last?

4h 22m, from 2026-10-06 11:58 UTC to 2026-10-06 16:21 UTC, by the times Harness posted.

What was affected?

Harness named Infrastructure as Code Management (IaCM).

What caused it?

Harness hasn't published a root cause. If it does, it shows here.

Where does this come from?

Harness's official status page, https://status.harness.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.