Jump to content

SQL > Important note on Status values in the JobStatuses table


Barrett Gardner

Recommended Posts

  • Cloud Solutions Architect

In JobStatuses, there is a 'status' value indicating the current state of a job. These enumerations are as follows:

1 = Unstarted

2 = Pending

3 = InProgress

4 = Paused

5 = Complete

6 = CompleteWithErrors

7 = Deleted

 

The status value of 6 applies to discovery jobs ONLY (jobtype = 4). Even though we will see data extract, processing and export jobs complete with errors, this status is determined by eCapture using a built-in procedure to identify any items during these job types that resulted in error (these will appear in JobStatuses as Status = 5 even though they report as "Completed with Errors" in the Controller UI).

 

Manually applying a status of 6 for any one of these jobtypes can result in unexpected behavior across the configuration environment such as errors thrown in the controller and Queue Manager for unrelated/inactive jobs, or intermittent halting of worker processes.

Link to comment
Share on other sites

  • Cloud Solutions Architect

In JobStatuses, there is a 'status' value indicating the current state of a job. These enumerations are as follows:

1 = Unstarted

2 = Pending

3 = InProgress

4 = Paused

5 = Complete

6 = CompleteWithErrors

7 = Deleted

 

The status value of 6 applies to discovery jobs ONLY (jobtype = 4). Even though we will see data extract, processing and export jobs complete with errors, this status is determined by eCapture using a built-in procedure to identify any items during these job types that resulted in error (these will appear in JobStatuses as Status = 5 even though they report as "Completed with Errors" in the Controller UI).

 

Manually applying a status of 6 for any one of these jobtypes can result in unexpected behavior across the configuration environment such as errors thrown in the controller and Queue Manager for unrelated/inactive jobs, or intermittent halting of worker processes.

Link to comment
Share on other sites

  • Cloud Solutions Architect

In JobStatuses, there is a 'status' value indicating the current state of a job. These enumerations are as follows:

1 = Unstarted

2 = Pending

3 = InProgress

4 = Paused

5 = Complete

6 = CompleteWithErrors

7 = Deleted

 

The status value of 6 applies to discovery jobs ONLY (jobtype = 4). Even though we will see data extract, processing and export jobs complete with errors, this status is determined by eCapture using a built-in procedure to identify any items during these job types that resulted in error (these will appear in JobStatuses as Status = 5 even though they report as "Completed with Errors" in the Controller UI).

 

Manually applying a status of 6 for any one of these jobtypes can result in unexpected behavior across the configuration environment such as errors thrown in the controller and Queue Manager for unrelated/inactive jobs, or intermittent halting of worker processes.

Link to comment
Share on other sites

  • 2 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...