Understanding event statuses

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

When to use this

Use this guide when you have found an event in the Control Panel and want to know what its status means and what, if anything, you need to do about it. Every event in the Control Panel has a status that tells you where it is in the processing pipeline.

For what a normal pattern of statuses looks like across a whole stream, see What a healthy integration looks like.

Before you start

Have the event open in the Control Panel. If you have not located it yet, see How to find a specific event in the Control Panel.
Note the event ID: you will need it if you contact HC.

Steps

Check the status and act on it

Open the event in the Control Panel.
Read its status.
Find the status in the table below and follow the action in the What to do column.

Status	What it means	What to do
New	The event has been created and is waiting to be transformed. This is normal for events that have just arrived.	Nothing at first. If it has not progressed after 15–30 minutes, investigate.
Transformed	The payload in has been transformed into the payload out. The event has not yet been sent to the destination system.	Nothing at first. If it has not progressed after 15–30 minutes, investigate.
Ok	The event data was sent to the destination system successfully.	No action needed.
Error	The transformation failed to transform the payload in.	Open the event to see the error detail.
Failed	The event data failed to 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. See "What to do with a failed event" below.
Aborted	The transformation detected a rule that stopped the event being sent. Most often this is duplicate prevention: the data has already reached the destination system, so HC aborts the event rather than sending it twice. Configured exclusions, such as test orders, also abort.	Nothing, if the data is already in the destination system. If it is genuinely missing, open the event to see which rule stopped it and contact HC.

What to do with a failed event

Open the failed event in the Control Panel.
Read the error message in the event detail.
If the error describes a missing or incorrect value that you can fix, go to How to fix and resend a failed event.
If you cannot identify the cause, go to I received an alert — what now? or contact HC with the event ID.

What you should see

You know what the status means and which action applies: nothing for Ok; wait, then investigate if it does not progress, for New and Transformed; the error detail for Error and Failed; and the rule that stopped it for Aborted.

If it did not work

You cannot find the event. Its job is often the faster route: find the run that should have carried it, then look at the events it created (see "How it works" below). For search and filter steps, see How to find a specific event in the Control Panel.

You cannot identify the cause of an Error or Failed status. Go to I received an alert — what now? or contact HC with the event ID: see How to get support.

How it works

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.

For the same list as a one-page reference, including the separate job statuses, see Event status definitions.

Was this helpful?

Still need help? Ask the team