AI Ready Pro / ZapTriage

Illustrative workflow review

Illustrative sample — not a customer result.

300 unique runs · 3 workflows · 2026-09-01T08:00:00.000Z to 2026-09-07T17:39:00.000Z (UTC)

Selection: all. Concern: errors. 0 identical duplicate records removed.

Customer-provided context: Illustrative data only. Lead delivery is marked business-critical for this example.

Investigation candidates

1. Inspect failed runs in Lead → CRM

Observation: 14 of 200 selected runs (7%) have an error status at export time.
Why this is prioritized: You marked this workflow as business-critical. Its affected runs take priority over non-critical workflows.
First check: Open the referenced runs in Zapier History. Compare the failed step and error message. Check whether the intended business records have since been processed.
If confirmed: If the same cause is confirmed, correct that specific step or its input. Check for records already created before replaying anything.
Verify the result: Check new relevant runs after the change, then reconcile the previously affected records in the destination app. A new successful run alone does not clear the backlog.
Certainty: Run statuses are observed within this export. The cause, current recovery state and impact on individual business records are not established.
Evidence: 10 of 14 affected run IDs: DEMO-0001, DEMO-0002, DEMO-0003, DEMO-0004, DEMO-0005, DEMO-0006, DEMO-0007, DEMO-0008, DEMO-0009, DEMO-0010

2. Check held runs in Order → Invoice

Observation: 3 of 60 selected runs (5%) have an on-hold status at export time.
Why this is prioritized: This workflow has one of the largest affected-run counts in this selection. Compare its business impact before making changes.
First check: Open the held runs and read the hold reason. Check the relevant app connection, account limits and any approval required. Confirm whether the runs are still waiting.
If confirmed: If the hold reason is confirmed, resolve that specific condition. Review each affected record before deciding whether to replay the run.
Verify the result: Check new relevant runs after the change, then reconcile the previously affected records in the destination app. A new successful run alone does not clear the backlog.
Certainty: Run statuses are observed within this export. The cause, current recovery state and impact on individual business records are not established.
Evidence: 3 of 3 affected run IDs: DEMO-0201, DEMO-0202, DEMO-0203

Workflow overview

Workflow	Runs	Error	Held	Known tasks
Lead → CRM lead-crm	200	14	0	372
Order → Invoice order-invoice	60	0	3	57
Weekly reporting weekly-report	40	0	0	40

What this report cannot establish

Conclusions apply only to the supplied selection, not to your entire account.
A run's status is a snapshot at export time. Subsequent recovery and business outcomes are not verified.
Workflow structure, error causes, replay relationships and financial savings are not inferred from names or run counts.

Report example · Source fingerprint: Illustrative sample · Method: status-triage-v1. A browser-supplied fingerprint identifies the selected file; it is not independent verification.

Downloaded copies are controlled by you and do not expire when the online report does.