Skip to main content
The token is a BPMN concept that represents a state within a process instance. It keeps track of the current position in the process flow and is used to store data related to the current process instance state. A token is created each time a new process instance starts. As actions on the process instance execute, the token advances from one node to the next. Because a node can have several actions that need execution, the token also tracks the actions executed in each node.
For parallel gateways, child tokens are created for each flow branch. The parent token moves to the gateway sync node and advances only after all child tokens reach that node.
The following diagram shows how a token advances through a process flow:

A token advances through a process flow

The token moves to the next node only after all mandatory actions from the current node are executed. The token also waits on a node if the node is configured to receive an event from an external system through Kafka.
Sometimes the token stops at a node until user input is received. If user input is required to advance the process, the token advances only after all data is received. Use a mandatory manual action linked to the user action to ensure the process flow advances only after the user input is received.

​
Viewing tokens

Retrieve the current process instance status using the FlowX Designer. The Designer displays information about tokens related to that process instance and the current nodes they are in.

​
Token view table

The token view displays tokens in a tree table format, providing a hierarchical view of parent and child tokens. This format is especially useful when working with parallel gateways or embedded subprocesses.
If parallel gateways are configured in a process, multiple tokens are created, one for each parallel path.

​
Token view features

Tree structure

Tokens are displayed hierarchically, showing parent-child relationships. All rows are expanded by default.

Horizontal scrolling

The table supports horizontal scrolling to accommodate all columns

Frozen columns

The UUID and Actions columns remain fixed when scrolling horizontally for constant visibility

Tooltips

Long names are truncated with tooltips showing the full text on hover
The token view table includes the following columns:
ColumnDescription
UUIDUnique identifier for the token. Only the first 6 characters are displayed with a copy icon. Clicking the icon copies the full UUID to clipboard. Frozen column (stays visible during horizontal scroll)
Token StatusCurrent state of the token in the process (ACTIVE, INACTIVE, ABORTED, ON HOLD, DISMISSED, EXPIRED, or TERMINATED). Displayed as color-coded tags
ContextShows the main process name for tokens in the main process, or the embedded subprocess name for tokens running within embedded subprocesses (any nesting level)
Initiator NodeThe node or event that initiated the token (for example, Parallel Gateway, Non-interrupting boundary event). Applies to child tokens only; displays ”-” for parent tokens
First Executed NodeThe node where the token first executed. For parallel gateway tokens, shows the first executed node on that parallel branch. For boundary event tokens, shows the first executed node on the branch started from the boundary node
Current NodeThe node where the token is currently positioned. For tokens in embedded subprocesses, displays the current node from the subprocess
Current Node StatusThe token’s status within the current node (ARRIVED, EXECUTING, EXECUTED_COMPLETE, EXECUTED_PARTIAL, WAITING_MESSAGE_EVENT, WAITING_TIMER_EVENT, WAITING_MESSAGE, MESSAGE_RECEIVED, or MESSAGE_RESPONSE_TIMED_OUT). Sortable column
Last updatedThe date and time when the token was last updated. Displays full datetime in browser timezone
ActionsAvailable actions including Retry (only visible for ACTIVE tokens) and View details (eye icon). Frozen column (stays visible during horizontal scroll)

​
Understanding token status

​
Token status values

The token status indicates the lifecycle state of a token in the process:
Token state is active when tokens are created. A parent token reactivates when all child tokens reach the parallel gateway closing node.
Child tokens become inactive when they arrive at a parallel gateway closing node. The current token becomes inactive when it reaches a final node.
The current token becomes aborted when it moves backward to redo a series of previous actions in the process. The token resets, and a new token activates.
When a parallel split gateway node is reached, the parent token is set to On hold until all child tokens reach the parallel gateway closing node. The parent token does not have a “Retry” action icon until all child tokens finish.
The process or subprocess reaches a certain node and is canceled or exited.
A defined “expiryTime” in the process definition passes, and the token changes to this status.
The process is terminated by a termination request.

​
Current node status values

The current node status indicates the execution status of the token within its current node:
The token reaches a new node
The token execution starts
Node actions execute, and all mandatory actions from the node complete
Node actions execute, but mandatory uncompleted actions remain
The token reaches an intermediate message catch event node
The token reaches an intermediate timer event node
The token waits for a message from another system
The message is received
The message is not received within the set timeframe

​
Initiator types

Tokens can be initiated by different sources. The initiator information is displayed in the Initiator Node column of the token view:

START_EVENT

Token initiated by a process start event. Parent tokens display ”-” in the Initiator Node column.

BOUNDARY_EVENT

Token initiated by a boundary event (for example, timer or message boundary event). The boundary event node name is displayed in the Initiator Node column.

PARALLEL_GATEWAY

Child token created by a parallel split gateway. The parallel gateway node name is displayed in the Initiator Node column.

SUBPROCESS

Token created for an embedded subprocess execution.
For tokens initiated by a BOUNDARY_EVENT within an embedded subprocess, the token context is preserved and the initiator node name is correctly mapped in the token view.

​
Viewing token details

To view more details about a token:
1

Open Process status

Click the Process status view button in the FlowX Designer.
2

Select a token

Select a token from the token list.
3

View details

Click the view button (eye icon) to open the detailed token status view.
Access the detailed token status view by navigating to Process instance → Tokens → View (eye icon). The detailed token status modal displays comprehensive information about the token’s current state, execution history, and configuration in a structured key-value format.

Detailed token status view showing token information, node details, and execution states

The detailed token status view presents token information in an expandable JSON-like structure. Key identifiers and status values are highlighted for quick identification. The modal includes the following fields organized by category:
  • id: The unique identifier of the token
  • version: The version number of the token schema
  • parentTokenId: The identifier of the parent token (present for child tokens created by parallel gateways or subprocesses)
  • processInstanceId: The identifier of the process instance this token belongs to
  • state: The current lifecycle state of the token (see Token status values for details)
  • statusCurrentNode: The execution status of the token within its current node (see Current node status values for details)
  • dateUpdated: The ISO 8601 timestamp indicating when the token was last updated
  • startNodeId: The identifier of the node where the token execution began
  • currentNodeId: The identifier of the node where the token is currently positioned
  • currentNodeName: The human-readable name of the current node
  • currentNode: Detailed information about the current node object
  • embedNodeId: The identifier of the embedded node, if the token is executing within an embedded subprocess
  • mainSwimlaneId: The identifier of the main swimlane associated with the token
  • currentProcessVersionId: The identifier of the process version currently being executed
  • currentContext: The current execution context (typically “main” for the main process, or the subprocess name for embedded subprocesses). This corresponds to the Context column in the token view table.
  • initiatorType: The type of initiator that created this token (see Initiator types for details)
  • initiatorId: The identifier of the initiator node or event
  • initiatorNode: The name of the node that initiated the token. This corresponds to the Initiator Node column in the token view table.
  • syncNodeTokensCount: The total number of synchronized node tokens (used for parallel gateway synchronization)
  • syncNodeTokensFinished: The count of synchronized node tokens that have finished execution
  • nodesActionStates: An expandable array containing detailed information about the action states for each node the token has visited. Each entry includes:
    • nodeId: The identifier of the node
    • context: The execution context (main or subprocess name)
    • embedNodeId: The embedded node identifier, if applicable
    • name: The name of the node
  • backSeq: An expandable object containing backward sequence information for tokens that have moved backward in the process flow:
    • nodesSeq: An array of node sequences that were executed in reverse order
    • uuid: The unique identifier for the backward sequence
    • context: The context where the backward sequence occurred
    • initiatorNode: The name of the node that initiated the backward sequence
    • firstExecutedNode: The first node executed in the backward sequence
    • currentNode: The current node in the backward sequence
  • paramValues: Parameter values and process variables associated with the token
The nodesActionStates and backSeq sections are expandable in the detailed token status view. Expand these sections to view comprehensive information about node execution history and backward sequence tracking.
Last modified on December 24, 2025