Why didn’t my automation run or finish on an order, and how do I check what it did?

An automation runs on an order only when it is enabled, its trigger fires for that order, and the order matches its conditions. Common reasons it did not run:

• The automation is a draft or disabled.
• The order arrived before the automation was enabled. Automations do not run on existing orders.
• The trigger did not fire. Order Approved fires only when a Draft is committed or a Pending order is approved, not for orders created as Ordered. Fulfillment Ready fires only when a fulfillment order is marked Ready.
• The order did not match the conditions. Endless does not record a run when conditions do not match.

Automations is in the main navigation. If your plan does not include it, the page says “Automations aren’t in your plan.”

Each automation’s page lists its Runs with a status: Complete, Failed, Skipped, Running, Pending, or Waiting. Expand a run to see each action’s result and the raw payload, which includes the order ID. Endless keeps runs for 3 days. On the order, the Timeline tab shows each change an automation made, with the automation’s name.

When an action fails, the run shows Failed with that action’s error, and the actions after it do not run. Other automations on the same trigger still run. An action skipped because its own conditions do not match does not stop the run.

The Process Fulfillment action skips a fulfillment order that already has a fulfillment rule, or that is already at or past the outcome you chose. Processing must be enabled. It fails when the order is on hold, inventory cannot be allocated in the building, a step’s requirements such as a shipping address or carrier service are not met, or the fulfillment order does not have a warehouse integration to send to. It acts once, so after you fix the cause, select the fulfillment order’s next action yourself. If the warehouse rejects a send, the fulfillment order shows Failed, and you can select “Resend for fulfillment.”