X4 Produktdokumentation

Status Values for Processes and Process Steps

During debugging and when executing a process, the X4 server provides status values for each process step and for executed processes. Any whole numbers (positive, negative, 0) are displayed as status values.

Note: Check the status values of the adapter you are using in the process to ensure that the adapter's status values do not collide with other status values in the process.

Recommendation: Use numbers greater than 1000 for user-defined status values to avoid possible overlaps with other status values.

Number

Label

Meaning

-999


Error status of the engine

Occurrence:

  • This error occurs with the engine problem No branch found to continue

  • The process cannot be started because it is broken

-998


The execution of the process was not carried out due to licence reasons.

Possible reasons:

  • no licence

  • damaged licence

  • expired licence

  • licence does not match the server version

-1

error

Error during execution of the process component (details are displayed in the server log).

The PID (process instance ID) displayed: The process is "Out of Service"

0

successful without result

The process component has been executed and there is no result document or the result is zero (empty).

1

successful

The process component was executed without syntactical errors.

997


The process was abruptly stopped (terminated) as planned (comparable to an uncaught exception in Java).
Causes the immediate termination of the entire process.

998


The process was (successfully) stopped and saved in a save point.
Causes the immediate termination of the entire process.

999


Status ID of process component not yet executed.

(any other negative integer)


Individual error status set by ConditionState mapping; ideally 4-digit; see

Set status dynamically with ConditionState

(any other positive integer)


Individual result status set by ConditionState mapping or by an adapter with variable status values; ideally 4-digit; see

Set status dynamically with ConditionState