Pylon incident

Delays in scheduled event processing

Minor Resolved View vendor source →

Pylon experienced a minor incident on May 26, 2026 affecting Data Warehouse and Triggers & Workflows and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 26, 2026, 06:45 PM UTC
Resolved
May 26, 2026, 06:45 PM UTC
Duration
Detected by Pingoru
May 26, 2026, 06:45 PM UTC

Affected components

Data WarehouseTriggers & WorkflowsBroadcasts

Update timeline

  1. investigating May 26, 2026, 06:07 PM UTC

    Status: Investigating Our engineering team is investigating an issue causing delays in processing some events within Pylon. We will post updates here and update impacted components as we have more information. Please reach out to Pylon support with any questions. Affected components Triggers & Workflows (Degraded performance) Broadcasts (Degraded performance)

  2. identified May 26, 2026, 06:16 PM UTC

    Status: Identified Our engineering team has identified the underlying cause and is working on a fix. This is affecting scheduled events (e.g. time delay triggers, scheduled messages and broadcasts, warehouse sync, etc.) and we do not anticipate any data loss as a result of this. Once the underlying issue is addressed, scheduled events will be processed. We apologize for any impact this is having on your operations, please reach out to Pylon support with any questions. Affected components Data Warehouse (Degraded performance) Broadcasts (Degraded performance) Triggers & Workflows (Degraded performance)

  3. monitoring May 26, 2026, 06:32 PM UTC

    Status: Monitoring Our engineering team has rolled out a fix, we are seeing queued events processing and we are monitoring. We will post another update here once we have confirmed this has been fully resolved. Please reach out to Pylon support with any questions. Affected components Broadcasts (Operational) Triggers & Workflows (Operational) Data Warehouse (Operational)

  4. resolved May 26, 2026, 06:45 PM UTC

    Status: Resolved Our engineering team has confirmed that this is now fully resolved - all queued events have been processed and new scheduled events are processing as normal. We appreciate your patience while we worked to address this, please reach out to Pylon support with any questions. Affected components Triggers & Workflows (Operational) Data Warehouse (Operational) Broadcasts (Operational)