Understanding event statuses

A guide to what each event status means and what action, if any, you should take.

Every event in the Control Panel has a status that tells you where it is in the processing pipeline.

Where events sit: jobs and entities

Events live inside jobs — each job is one run of a stream, and it creates one event per record it finds in the source system. Events in turn create or update entities, the tracking records HC uses for deduplication. If you cannot find an event, its job is often the faster route: find the run that should have carried it, then look at the events it created.

Status definitions

Ok — The event completed successfully. Data was delivered to the destination system. No action needed.

Failed — The event could not be sent to the destination system. Open the event to see the error detail. If the error is something you can correct from the Control Panel, fix and resend it. If not, contact HC.

Error — The event could not be transformed. Open the event to see the error detail.

Transformed — The event has been transformed but has not been sent to the destination system. This is normal for events that have just arrived. If an event has been pending for more than 5-10 minutes, investigate.

Aborted — The event was deliberately excluded from processing by a configured rule. For example, test orders in Shopify are typically configured to skip. If you see a skipped event that you expected to process, open the event to see which rule caused the skip, and contact HC if the skip was unintended.

What to do with a failed event

  1. Open the failed event in the Control Panel.

  2. Read the error message in the event detail.

  3. If the error describes a missing or incorrect value that you can fix: go to How to fix and resend a failed event.

  4. If you cannot identify the cause: go to I received an alert — what now? or contact HC with the event ID.