Prod 2 - Customers may see some executions from March 11 in a "running" but hung state

What to do

• Check whether you use Harness Continuous Delivery - Next Generation (CDNG). 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 2h 56m it lasted.

  Anything that failed between 2026-03-12 16:20 UTC and 2026-03-12 19:16 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 3

1. investigatingMar 12, 2026, 4:20 PM UTC

   Customers may continue to see that some pipeline executions show that they are "running" even though they have completed, aborted, or failed as a result of yesterday's incident. (https://status.harness.io/incidents/4y4dl47v2qhc) This behavior is a UI-only artifact from the incident and should not affect customers' ability to start new executions.  We are working on clearing these artifacts.

   provider

2. identifiedMar 12, 2026, 4:21 PM UTC

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

   provider

3. resolvedMar 12, 2026, 7:16 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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