Job Info
A TIF Job is an entity that holds together the input to the execution, the result of the execution, the status / progress of the execution and other information required to be able to execute the job.
Whenever an inbound event from 3DEXPERIENCE™ is mapped by an event mapping, an inbound REST call is mapped by a REST Mapping or a Scheduled Task is being triggered, a new Job entity is created within the TIF database.
Once a job is being created, it will be attached to a service which is responsible for the execution of the job logic.
A job will be transitioned along a couple of states during its lifetime.
The states a Job can have are described below:
| State | Description | Is Final State |
|---|---|---|
Created |
The initial state of a job |
No |
Started |
Once picked up by an executor, the state of the job is changed to "Started". |
No |
Completed |
The state a job gets when executed with a successful outcome |
Yes |
Failed |
The state a job gets when execution fails. |
Yes |
Failed Retrying |
The job has failed, but it will be re-executed |
No |
Awaiting Reply |
The job has been completed. It has sent out some data to another system that we now are awaiting some asynchronous reply from. Once we receive the reply from the other system, the state of this job will be transitioned to either the state completed or failed. |
No |
Cancelled |
If a job was canceled during the execution, the job gets this state. Note that cancelled jobs will be removed automatically from the system |
Yes |
Moreover, if a Job has failed, an administrator may be able to identify the reason and by so also mark the Job as being resolved with an optional description of the root cause. Resolved jobs are still considered to be 'Failed', but has the 'resolved' flag set.
|
If a job is attached to a service that is paused, the state for the Job will in the Administration UI be shown as Paused even though the state of the Job actually is 'Created'. Paused is just a virtual state for a Job in the Administration UI. |