---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Event states

# Event states {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The event state describes where in the life cycle the event is.
{#r_EventStates__table_hb4_bk3_wr__entry__2}

| State | Description |
|-|-|
| Ready | The system created the event and it is in the queue waiting to be processed. |
| Processed | The event successfully ran. An event does not necessarily trigger any further action when processed. Additional functionality must make use of the event. |
| Error | The event encountered an error during processing. This state is often caused by invalid event parameters. Reprocessing the event may resolve the error. |
| Transferred | The event was rotated to a different shard of the Event \[`sysevent`\] table. When an event is rotated, a duplicate record is created in an active shard to be processed. A scheduled job processes the event when it is next in the queue, but it is not possible to predict when this will happen as because several events may need to be processed before it. Therefore, you can reprocess the event. See [Reprocess an event](https://servicenow-prod.fluidtopics.net/yQfis_iuXWwCfqyFUAdgfQ "You can fire the event again for testing or diagnostic purposes."). |
[Table 1. Event states]

{#r_EventStates__table_hb4_bk3_wr}