Job Statuses

www.altova.com Print this Topic Previous Page Up One Level Next page

Home >  Monitoring Job Execution >

Job Statuses

Across its lifetime, a job instance gets various statuses, as indicated by the Status column in the Running jobs table.

fs_monitoring_01

The following diagram illustrates how a job instance typically changes from one state to another across its lifetime. It is assumed that no loss of FlowForce Server service or network interruptions occurred. Note that some of the statuses take a very short time span and will not normally be visible in the user interface.

ff_job_statuses_diagram

 

The following table lists all the possible statuses of a job.

 

Status

Description

Created

This is the first state the job is in, before any other action takes place. The next possible states are Starting, Waiting, Queued, Failed, and Aborted.

Waiting

This status may happen for a job instance triggered as a result of a file system or HTTP trigger. It indicates that the job instance was triggered but the settle period specified by the Wait N seconds for settle option has not elapsed yet.

Queued

Indicates that the job instance was triggered but the execution queue is currently full. An execution queue has a limited number of slots, so only the specified number of job instances can execute in parallel on the same queue, see also Defining Queue Settings. Any further instances arriving for that queue will wait until a slot becomes free, and will appear as having the Queued status.

 

Usually, the next status after Queued is Starting, unless interruptions occur.

Starting

This status is usually very brief; it means that the job instance has been assigned a free queue slot and will soon start executing the first step.

Running

Indicates that the job instance is currently running and will stay in this state until execution is complete or until some external event occurs that ends execution prematurely. Except for a very brief time window in the beginning, this status has a step number associated with it, such as Running step {step}.

Failed

Execution of this job instance has finished and was considered a failure. This is a final status and there will be no further attempts to run the job instance.

 

A Failed after step {step} status additionally indicates that the failure is associated with a step number.

Finished successfully

This is a final state which indicates that the job has completed successfully.

Aborting

The job instance is attempting to finish execution because a FlowForce user has stopped it by clicking the Stop job button. Note that stopping the job is an asynchronous action which may take time, and a job instance may actually be able to complete successfully before it transitions to the Aborted state. If this happens, the job will be reported as having finished successfully.

 

If the previous status had a step number, then the Aborting after step {step} status is shown instead of Aborting.

Aborted

The job instance has finished execution. Normally, this status indicates that a user has stopped the job, although it may also occur indirectly after an unexpected shutdown. This is a final state and it indicates that at least some part of the job hasn't finished.

 

If the previous status had a step number, then the Aborted after step {step} status is shown instead of Aborted.

Interrupted

The execution of the job instance was interrupted (for example, because a network cable was unplugged, the worker machine has crashed or was shut down, and similar force-terminated events). This is a more forceful variation of the Aborted state. The job instance cannot be restarted so it should be treated as failed. There is no guarantee about the consistency of the job, so it is recommended that you check its outcome manually.

Lost connection

Applicable when multiple FlowForce instances run as a cluster.

 

This status indicates that the master machine has lost the connection to the worker machine. There is currently no way to reasonably determine the status of this job instance. Better state information may become available when the worker is back.

Synchronizing

Applicable when multiple FlowForce instances run as a cluster.

 

In a clustered setup, the master machine periodically gets the current progress of job instances from the worker machines. This status indicates that the connection to the worker has been restored after it was lost, and FlowForce is attempting to obtain the latest status from the worker.

Untracked

Indicates that the FlowForce Server process is currently unable to track the job. This status may occur when the master unexpectedly went down while the job was still running on a worker machine.

 

There is a subtle difference between Interrupted and Untracked: In the former case, FlowForce Server knows it was terminated as a process, whereas in the latter case it just isn't aware of what exactly has happened.

 

Like with Interrupted, there is no guarantee about the consistency of the job, so it is recommended that you check its outcome manually.

Superseded

This status signifies an uncritical termination of a job before the job had actually the chance to do something. This is not a critical condition. It essentially means that FlowForce Server has detected a further change and thus canceled the previous job instance and created a new one.

 

For example, this status may happen for a job instance triggered as a result of a file system or HTTP trigger. If the file triggering the job has changed before the settle period specified by the Wait N seconds for settle option, then the job instance may get this status.

 

This status can also occur with time triggers, if the time trigger was triggered again while a previously started instance is still waiting for a slot.


© 2019 Altova GmbH