Skip to main content

Event log

In briefThe event log is the record of every event the platform processed: where it came from, what it changed, and whether it succeeded. Each event carries a correlation ID, so you can follow one action through everything it set off.

WhereOperations › Event Log. It shows the environment selected at the top of the Operations section of the navigation; switch environment there.

When

  • An event — from a job, a self service button, the API, a webhook or an agent — did not do what you expected.
  • You want to see what one action set off, through its correlation ID.
  • You want to know what a property token resolved to on a particular attempt.
  • A FAILED event needs explaining before anyone raises it again.

Use something else when you need to know what a job did: its Output and Status History are on the Processes page.

How

  1. Open Operations › Event Log, and check the environment selected above it in the navigation.
  2. Narrow the list by Status, Event Type, Source, User or date.
  3. Select an event to read its Payload, State Changes, Attempts and Error.
  4. Select its Correlation ID to see every event from the same action.

For the full steps, see Use the event log.

Notes
  • The payload is stored as it was authored. Property tokens are resolved each time the event is processed, and Attempts shows what each one resolved to.
  • An event refused before it became an event — an agent's event line with the wrong field count, for instance — has no row here.
  • A job or workflow event refused for a name that would add extra tags or entries is recorded as FAILED, with the reason; nothing in it was applied. So is an event that would create a property whose name holds a token that did not resolve.
  • The list refreshes itself every 10 seconds by default; pause it while you read.
  • Reading the log needs the Audit History View permission, which applies tenant-wide.
Watch out
  • There is no Retry in the event log. To run a failed event again, raise it again from where it came from.
  • A $JOB:ADD that partly failed is not safe to raise again as it stands. Read its error first.
  • A not supported error is permanent. Remove or replace the event rather than raising it again.