Re-Do Error Runs

A manual repair tool that reprocesses previously failed ShipHero-shipment runs. It replays the failing node's logic against Supabase, backfilling shipment, order, line-item, and Product SKU data that earlier errors left missing.

At a glance

• Status: Inactive (manual only).
• Trigger: Manual ("When clicking 'Test workflow'").
• Runs on: Unsolved rows in the Supabase Failed runs table (is_solved = false).
• Talks to: Supabase, ShipHero GraphQL, and the n8n internal API.

How it works

1. Get Unsolved Error runs pulls Supabase Failed runs where is_solved = false.
2. The n8n node fetches the original execution details by execution_id.
3. A Switch branches on the failed node_name to resume from the right point.
4. Branches recreate the original pipeline: warehouse lookup, parse packages, insert Shipments, find the Order, expand line items, insert Shipment Line Items, then create and link Product SKUs via the m2m table.
5. Where needed, it fetches order details from ShipHero and patches the Shipments row with the Orders_id.

Notes

• Manual repair and backfill tool, not scheduled.
• Relies on the original execution's data still being available; it references a Webhook node that is not present in this workflow, so it only works while that source data persists.

Related

• Reattempt Failed Runs: a sibling retry tool for the retired queue flow.
• OLD: ShipHero Shipment → Queue: the retired ingestion whose failures this repairs.
• Missing Shipment Data Pull (v1): the current shipment ingestion that superseded the old pipeline.
• Error Handler: the shared error workflow.
• See also Data flows.