X4 Produktdokumentation

Status Values for Processes and Process Steps


During debugging and running a process, the X4 Server provides status values for each process step and for executed processes. The status values are displayed as integers (positive negative, 0).


Note: Check the status values of the adapter you are using in the process to make sure that the status values of the adapter do not clash with other status values in the process.


Recommendation: Use integers larger than 1000 to define custom status values to prevent overlaps with other status values.


Number

Label

Meaning

-999


Engine failure status

Occurrence:

  • In the event of an engine problem, the following message appears: No branch found to continue

  • The process cannot be started because the process is defective.

-998


The process was not executed for licensing reasons.

Possible reasons:

  • No license

  • A corrupted license

  • An expired license

  • A license that does not match the server version

-1

error

Error when executing the process component (details are displayed in the server log)

The following is displayed as PID (Process Instance ID): 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 null (empty).

1

successful

The process component was executed without syntactic errors.

997


The process was scheduled to stop abruptly (scheduled) (similar to an unintercepted exception in Java).

Causes the entire process to terminate immediately.

998


The process has been stopped (successfully) and saved to a Savepoint.

Causes the entire process to terminate immediately.

999


Status ID of process components that have not yet been executed

(Any other negative integer)


Individual error status set usingConditionState mapping; ideally 4-digit; see Setting Status Dynamically with ConditionState

(Any other positive integer)


Individual result status set by means of ConditionState mapping or by an adapter with variable status values; ideally 4-digit; see Setting Status Dynamically with ConditionState