CM.com incident

HALO - tool call failures

Minor Resolved View vendor source →

CM.com experienced a minor incident on May 7, 2026 affecting Studio, lasting 3h 59m. The incident has been resolved; the full update timeline is below.

Started
May 07, 2026, 08:50 AM UTC
Resolved
May 07, 2026, 12:49 PM UTC
Duration
3h 59m
Detected by Pingoru
May 07, 2026, 08:50 AM UTC

Affected components

Studio

Update timeline

  1. investigating May 07, 2026, 08:50 AM UTC

    We've received and validated reports for HALO of tool call failures when LLM interactions or Agentic Steps are used. We've identified the cause and are working to resolve this.

  2. identified May 07, 2026, 08:50 AM UTC

    We've received and validated reports for HALO of tool call failures when LLM interactions or Agentic Steps are used. We've identified the cause and are working to resolve this.

  3. identified May 07, 2026, 09:05 AM UTC

    We've received and validated reports for HALO of tool call failures when Agentic Steps are used. We've identified the cause and are working to resolve this.

  4. monitoring May 07, 2026, 09:20 AM UTC

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

  5. resolved May 07, 2026, 12:49 PM UTC

    This incident has been resolved.

Looking to track CM.com downtime and outages?

Pingoru polls CM.com's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when CM.com reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track CM.com alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring CM.com for free

5 free monitors · No credit card required