Incident example

From broken signal to actionable proof.

This example shows how CashFlowCanary turns a WooCommerce checkout failure into a readable incident: what is detected, what is proven, what should be fixed and how resolution is confirmed.

Free audit See the PDF

Scenario

A deliberately fictional example designed to show the reporting format without exposing a real store.

Detection

The product -> cart -> checkout journey remains reachable, but payment validation returns an observable error on the final step.

Proof

The report keeps time, step, status, error class and useful technical context, without customer email or cart contents.

Diagnosis

The likely cause points to a payment method configuration or checkout incompatibility after a store change.

Action

The team checks the active payment method, relevant plugin, checkout cache and reruns verification after the fix.

Shareable proof

The proof says what to fix, not only that the site is red.

A useful incident stays readable by a merchant, actionable by an agency and verifiable by a developer. The format focuses on the next action rather than a raw error screen.

Exact funnel step
Likely cause and priority
Resolution confirmed after green checks

See the 24h deliverable See pricing

Filtered CashFlowCanary incident proof example

Fictional example: June 17, 2026

1. Detection

At 09:14, the priority checkout check observes that the payment page still responds, but the finalisation attempt fails. The incident opens because the failure affects a revenue step.

2. Proof

Affected page: checkout.
Error class: payment not completed.
Kept signal: status, step, latency, timestamp and filtered technical excerpt.
Excluded signal: card data, customer identity, detailed cart contents.

3. Recommended diagnosis

The diagnosis prioritises checking the active payment method, checkout module, cache and recent WooCommerce changes. The message is written so it can be passed to the fixing team.

4. Resolution

After correction, a new verification turns the journey green. The incident can be closed with before/after proof and the report remains available according to plan rights.