Skip to main content
Reference

Event status definitions

A complete reference for every status an event can have in the Control Panel.

Status reference

The statuses below are listed in the order an event moves through them.

Status

What it means

Action needed?

New

The event has been created and is waiting to be transformed.

None β€” unless it has not progressed after 15–30 minutes

Transformed

The payload in has been transformed into the payload out. The event has not yet been sent to the destination system.

None β€” unless it has not progressed after 15–30 minutes

Ok

The event data was sent to the destination system successfully.

None

Error

The transformation failed to transform the payload in. The error detail is in the event view.

Yes β€” investigate and fix, or raise it with HC

Failed

The event data failed to be sent to the destination system. The error detail is in the event view.

Yes β€” investigate and fix, or raise it with HC

Aborted

The transformation detected a rule that stopped the event being sent. The most common 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.

Only if you expected the event to be sent

How to act on failed or unexpected statuses

Error or Failed β€” go to I received an alert β€” what now? or How to fix and resend a failed event.

New or Transformed for more than 15–30 minutes β€” go to An event hasn't arrived in the destination system.

Aborted unexpectedly β€” open the event to see which rule stopped it. If the data really is missing from the destination system rather than already there, contact HC.

Job status definitions

Jobs β€” single runs of a stream β€” have their own statuses, which are separate from the event statuses above:

Pending β€” the job is scheduled to run but has not started yet.

Processing β€” the job is running and creating events.

Finished β€” the job completed and all of its events processed successfully.

Finished with issues β€” the job completed, but some of its events failed or saw issues.

Failed β€” the job itself failed in the source system; usually no events were created at all.