Diagnose a Stuck Order - Fluent AI Skills
How-to Guide
Author:
Fluent Commerce
Changed on:
31 Mar 2026
Key Points
[Warning: empty required content area]Prerequisites
Steps
Trace the order
`Why is order HD-12345 stuck in BOOKED?`Runs
`event_flowInspect` on the order, analyzing all orchestration events to find: - Which events fired and which NO_MATCHed - Failed webhook deliveries - Rulesets that should have triggered but didn't - Timeline of every status changeIf you want the combined runtime-vs-workflow report instead of runtime triage alone, say:`Compare runtime vs workflow for order HD-12345`That routes to
`/fluent-entity-flow-diagnose`, which reconstructs the dynamic chain, resolves the relevant workflow set, and shows expected vs observed behavior in one report.Check available actions
`What actions can I take on this order right now?`Queries the Transition API for user actions available at the current status — shows event names, required attributes, and button labels.
Fire a remediation event
`Send a RetryFulfilmentAllocation event to order HD-12345`Builds and sends the event (with dry-run preview first), then monitors the result.
