View Job Status - EcoSys - 3.1 - Help - Hexagon

Running

The job is running.

Success

Job is executed successfully. This does not mean that all the data is created as expected.

If no rows are read from a reader, the job will end with a success. To know how the job executed,

• Enable write statistics and review them

• Review the execution history

Failed

The job fails due to configuration issue, API Failure/Fault/unavailable, API timeout.

Stopped

Jobs that are running during a restart of the agent.

Timeout

Dispatcher server setting dispatcher.default.stepExecution.timeout.minutes controls it. (default 60).

• The job takes too long to execute.

• The job was never executed ( Reasons might be no queue and Agent was available).

Canceled

The user canceled job manually via Connect UI

• The job started from an EcoSys Action and had timeout set explicitly on the action which has expired before the job completed.

• The job started from an EcoSys Action and was cancelled by it before it was completed.