Coalesce incident

Transform North America: Job Execution Service Interruption

Minor Resolved View vendor source →

Coalesce experienced a minor incident on April 30, 2026 affecting us-central1, lasting 17h 8m. The incident has been resolved; the full update timeline is below.

Started
Apr 30, 2026, 09:15 PM UTC
Resolved
May 01, 2026, 02:23 PM UTC
Duration
17h 8m
Detected by Pingoru
Apr 30, 2026, 09:15 PM UTC

Affected components

us-central1

Update timeline

  1. identified Apr 30, 2026, 09:15 PM UTC

    Coalesce Transform for customers in our North America region experienced a service degradation starting on Wednesday April 29th with the release of 7.33 that is affecting job execution. - Root cause: A change in 7.33 made our node selector matching case-insensitive, which in a rare circumstance, made it possible for newly created jobs enter a recursive job-launch loop. - Current state: We have applied a concurrency limit that prevents runaway job launches and are working on a hotfix to resolve the underlying issue. - Fix inbound ASAP: Hotfix reverting selector matching to case-sensitive is approved and in our release pipeline now. We will update this incident once resolved.

  2. monitoring Apr 30, 2026, 09:45 PM UTC

    The hotfix has been delivered in version 7.33.2

  3. resolved May 01, 2026, 02:23 PM UTC

    The incident has been resolved.