Query flow node instances
POST/flownode-instances/search
Search for flow node instances based on given criteria.
Request
- application/json
Body
- Array [
- ]
sort object[]
Sort field criteria.
The field to sort by.
Possible values: [ASC
, DESC
]
Default value: ASC
The order in which to sort the related field.
page object
Pagination criteria.
The index of items to start searching from.
The maximum number of items to return in one request.
Items to search after. Correlates to the lastSortValues
property of a previous search response.
Items to search before. Correlates to the firstSortValues
property of a previous search response.
filter object
Flow node instance filter.
The assigned key, which acts as a unique identifier for this flow node instance.
The process instance key associated to this flow node instance.
The process definition key associated to this flow node instance.
The process definition ID associated to this flow node instance.
Possible values: [ACTIVE
, COMPLETED
, TERMINATED
]
State of flow node instance as defined set of values.
Possible values: [UNSPECIFIED
, PROCESS
, SUB_PROCESS
, EVENT_SUB_PROCESS
, START_EVENT
, INTERMEDIATE_CATCH_EVENT
, INTERMEDIATE_THROW_EVENT
, BOUNDARY_EVENT
, END_EVENT
, SERVICE_TASK
, RECEIVE_TASK
, USER_TASK
, MANUAL_TASK
, TASK
, EXCLUSIVE_GATEWAY
, INCLUSIVE_GATEWAY
, PARALLEL_GATEWAY
, EVENT_BASED_GATEWAY
, SEQUENCE_FLOW
, MULTI_INSTANCE_BODY
, CALL_ACTIVITY
, BUSINESS_RULE_TASK
, SCRIPT_TASK
, SEND_TASK
, UNKNOWN
]
Type of flow node as defined set of values.
The flow node ID for this flow node instance.
The flow node name.
Shows whether this flow node instance has an incident related to.
The key of incident if field incident is true.
The tenant ID.
Responses
- 200
- 400
- 401
- 403
- 500
The flow node instance search result.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
page object
Pagination information about the search results.
Total items matching the criteria.
The sort values of the first item in the result set. Use this in the searchBefore
field of an ensuing request.
The sort values of the last item in the result set. Use this in the searchAfter
field of an ensuing request.
items object[]
The matching flow node instances.
The assigned key, which acts as a unique identifier for this flow node instance.
The process instance key associated to this flow node instance.
The process definition key associated to this flow node instance.
The process definition ID associated to this flow node instance.
Date when flow node instance started.
Date when flow node instance finished.
The flow node ID for this flow node instance.
The flow node name for this flow node instance.
Possible values: [UNSPECIFIED
, PROCESS
, SUB_PROCESS
, EVENT_SUB_PROCESS
, START_EVENT
, INTERMEDIATE_CATCH_EVENT
, INTERMEDIATE_THROW_EVENT
, BOUNDARY_EVENT
, END_EVENT
, SERVICE_TASK
, RECEIVE_TASK
, USER_TASK
, MANUAL_TASK
, TASK
, EXCLUSIVE_GATEWAY
, INCLUSIVE_GATEWAY
, PARALLEL_GATEWAY
, EVENT_BASED_GATEWAY
, SEQUENCE_FLOW
, MULTI_INSTANCE_BODY
, CALL_ACTIVITY
, BUSINESS_RULE_TASK
, SCRIPT_TASK
, SEND_TASK
, UNKNOWN
]
Type of flow node as defined set of values.
Possible values: [ACTIVE
, COMPLETED
, TERMINATED
]
State of flow node instance as defined set of values.
Shows whether this flow node instance has an incident. If true also an incidentKey is provided.
Incident key associated with this flow node instance.
The tenant ID of the incident.
{
"items": [
{
"flowNodeInstanceKey": 0,
"processInstanceKey": 0,
"processDefinitionKey": 0,
"processDefinitionId": "string",
"startDate": "2024-12-13T13:19:42.551Z",
"endDate": "2024-12-13T13:19:42.551Z",
"flowNodeId": "string",
"flowNodeName": "string",
"type": "UNSPECIFIED",
"state": "ACTIVE",
"hasIncident": true,
"incidentKey": 0,
"tenantId": "string"
}
],
"page": {
"totalItems": 0,
"firstSortValues": [
{}
],
"lastSortValues": [
{}
]
}
}
The Flow node instance search query failed. More details are provided in the response body.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}
The request lacks valid authentication credentials.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}
Forbidden. The request is not allowed.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}
An internal error occurred while processing the request.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}