Harness incident

Intermittent error while loading template service page

Notice Resolved View vendor source →

Harness experienced a notice incident on January 8, 2026 affecting Continuous Delivery - Next Generation (CDNG), lasting 5h 23m. The incident has been resolved; the full update timeline is below.

Started
Jan 08, 2026, 07:03 PM UTC
Resolved
Jan 09, 2026, 12:26 AM UTC
Duration
5h 23m
Detected by Pingoru
Jan 08, 2026, 07:03 PM UTC

Affected components

Continuous Delivery - Next Generation (CDNG)

Update timeline

  1. monitoring Jan 08, 2026, 07:03 PM UTC

    A fix has been implemented and we are monitoring the results.

  2. resolved Jan 09, 2026, 12:26 AM UTC

    This incident has been resolved.

  3. postmortem Jan 16, 2026, 05:36 AM UTC

    ### **Incident Overview** On January 8, 2026, between 10:25 AM and 10:47 AM UTC, the Harness Template Service experienced authentication failures, preventing customers from loading templates. **Impact**: Customers were unable to load templates in the Harness UI. No running pipelines were affected. ### **Root Cause** During a scheduled secret rotation, one database user credential errored out during rotation. This caused the Template Service to lose database authentication, resulting in service failures. ### **Mitigation Actions** * **Immediate Response** * Re-enabled the old database user to restore Template Service authentication and functionality. * **Resolution** * Service was fully restored within 2 minutes of detection. ### **Next Steps and Improvements** * Adding a verification step to confirm the new user is active in GCP Secret Manager before disabling the old user in the database. * Enhancing the secret rotation process to prevent similar gaps in credential updates