Coalesce incident
Transform North America: Job Execution Service Interruption
Affected components
Update timeline
- 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.
- monitoring Apr 30, 2026, 09:45 PM UTC
The hotfix has been delivered in version 7.33.2
- resolved May 01, 2026, 02:23 PM UTC
The incident has been resolved.
Looking to track Coalesce downtime and outages?
Pingoru polls Coalesce's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Coalesce reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Coalesce alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required