Skip to content
MindflowMindflowMindflow Help Center

Incident Report 24/08/2026

Start: August 23, 2026, ~10:00 AM UTC+2

Identified: August 24, 2026, ~11:26 AM UTC+2

End: August 24, 2026, ~11:30 AM UTC+2

Reach: Webhooks using the affected Artifacts quota-control path

Impact: High — Webhooks no longer triggered flows; users saw a generic execution acknowledgement but no execution followed

Description

Section titled “Description”

On August 24, 2026, a customer reported that webhook-triggered flows were no longer starting. The visible response was:

“Your playbook is going to be executed. Stay tuned…”

However, no execution followed. Mindflow investigated immediately, fixed the issue, and restored the customer environment. Customer confirmed that webhooks were working again across the affected flows shortly afterward.

The incident was linked to the Artifacts feature (beta).

Cause

Section titled “Cause”

The issue was caused by a size limit on a numeric value passed through Mindflow APIs.

Artifact data is measured in bytes. For this customer, the value passed into quota control exceeded what the GraphQL API accepted for that field. As a result, the quota-control path rejected or failed the request before webhook-triggered executions could proceed.

This specific scale of value had not previously occurred for Mindflow customers, likely because Artifacts is a recent feature and this is one of the first cases reaching this data-size range.

Impact

Section titled “Impact”
  • Affected capability: webhook-triggered flow execution.
  • Symptom: webhooks returned the generic “playbook is going to be executed” acknowledgement, but the corresponding flow did not start.
  • Customer-visible effect: webhook-based automations were blocked until Mindflow fixed the affected path.
  • Unaffected: flows not relying on the affected webhook / Artifacts quota-control path.

Resolution

Section titled “Resolution”

Mindflow fixed the affected customer path on August 24, 2026, which restored webhook execution. The quota-control API now accepts the relevant byte-size value safely to prevent this class of failure from recurring.

Follow-up

Section titled “Follow-up”
  • Monitor the GraphQL quota-control path to confirm byte-size values continue to be handled safely at the expected scale.
  • Add regression coverage for large byte-size values in Artifacts quota checks.