# Few customers experiencing intermittent errors during pipeline execution.

- Provider: [Harness](https://down.guide/providers/harness)
- Confidence: Confirmed
- Impact: Degraded
- lasted 1h 25m
- started 2026-07-09 20:21 UTC
- Continuous Delivery (CD) - FirstGen - EOS, Continuous Integration Enterprise(CIE) - Linux Cloud Builds
- id: DWN-1339cd8cfe
- Official page: https://stspg.io/fv5drkv33y06

## Updates from Harness
### 2026-07-09 20:21 UTC: investigating
We are currently investigating this issue.

### 2026-07-09 21:10 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2026-07-09 21:46 UTC: resolved
This incident has been resolved.

### 2026-07-21 05:21 UTC: postmortem
Summary
On July 9, 2026, some customers in the Harness Prod3 cluster experienced pipeline failures over a ~2.5-hour window, despite making no changes in their pipelines. Shell Script steps failed when fetching scripts from the Harness File Store, and Kubernetes deployment steps failed when retrieving secret encryption details.
Impact
1. Affected users: Some customers using the Harness Prod3 cluster reported pipeline execution failures.
2. User impact: Customers experienced failures in Shell Script and Kubernetes deployment steps. Impacted pipelines required manual retries after the incident was resolved.
3. Scope: This was not a platform-wide outage. The issue was isolated to specific APIs in our internal service within the Prod3 cluster.
Root Cause
The incident was caused by degraded performance in a downstream service. This led to a storm of timeout errors in our internal service, which caused these failures.
Mitigation
Engineering identified the change that caused this issue in the downstream dependency service and deployed a patch to restore it. Once deployed, pipeline executions returned to normal success rates.
Preventive Measures & Next Steps
1. Added additional monitoring and alerting on the downstream service to detect performance degradation earlier.
2. Reviewing timeout and retry logic in the internal service to improve resilience against downstream latency spikes.
3. Evaluating circuit breaker patterns to prevent cascading failures from downstream dependencies.

From the builder: does your app depend on Harness? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=harness) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Harness.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-1339cd8cfe), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.