Skip to main content

End Event 🎯

Marks the completion of a workflow execution path.

Node type: endEvent Category: Flow Control Actor: endEvent (1 thread)

Description​

The End Event signals the termination of an execution path. When all paths in a workflow reach an End Event, the process instance is marked as Completed (stateCd: 1).

A workflow can have multiple End Events — for example, one for the success path and one for the failure path.

Properties​

The End Event has no configurable properties. All common node properties (timeout, retry, loop) do not apply.

Inputs​

The End Event receives the current execution context (all variables accumulated throughout the workflow). These final variable values are stored on the process instance as the data field and are accessible via the Executions API.

Outputs​

No outgoing connections. The End Event terminates the execution path.

Connections​

FromConnection TypeTo
Any nodesequenceFlowEnd Event

The End Event can only have incoming connections — never outgoing.

Multiple End Events​

A workflow can have multiple End Events for different terminal conditions:

[Start] → [Classify Issue]
                ↓ trueFlow (billing)
         [Send to Billing Team] → [End Event: Billing]
                ↓ falseFlow (other)
         [Send to Support Team] → [End Event: Support]

Both paths converge on separate End Events. The process instance completes when the active path reaches its End Event.

Final Execution Data​

When execution reaches an End Event, the final value of all workflow variables is captured as the process instance data. This can be retrieved via:

GET /process/instance/{processInstanceId}
{
  "processInstanceId": "inst_xyz789",
  "stateCd": 1,
  "data": {
    "customerName": "Jane Smith",
    "classification": "billing",
    "responseText": "Your billing issue has been escalated.",
    "ticketId": "TKT-5521"
  }
}

Notes​

  • A workflow must have at least one End Event
  • In parallel workflows, all active paths must complete (reach an End Event or a Join node) for the instance to be marked Completed
  • If a node fails without an error flow, the process instance is marked Failed (stateCd: 2) even if no End Event is reached