Scheduled Jobs (ttaad5120m000)

Use this session to show an overview of all scheduled jobs across all companies.

Actions/Buttons

These options are available:

Initialize
Starts initializing the jobs.

Field Information

Tenant

The name of the tenant.

Company

The company in which the job is created.

Job

Job code.

User

The owner of the job.

Planned Execution Date

Shows the date/time when the job will be started.

Actual Execution Date

Shows the date/time when the job was actually started.

Expiry Date

Shows the expiry date/time of the job. This date/time is set by the scheduler after claiming the job. If the job is not started by the scheduler before this date/time, a new attempt is made to start the job.

Status

The status can have different values.

  • Waiting

    The job is waiting to be carried out at the next planned execution date and time.

  • Starting

    The job is claimed by the scheduler and the bshell to run the job is started.

  • Running

    The bshell to run the job was started successfully and the job is running.

  • Failed to Start

    The bshell to run the job was not started successfully and an error is logged for the job. Later, a new attempt will be made to start the job.

  • Postponed

    The job is not started by the scheduler because downtime is defined. See the Planned Downtime (ttaad5530m000) session.

  • Running Failure

    A failure is encountered during the execution of the job. You can use the last recorded date/time in the Job Tick field to search the log and determine the reason for the failure.

Hostname

The name of the server where the job is running.

Bshell ID

The process ID of the bshell starting the job, when the job is running.

Job Tick

After starting a job, this field is updated every minute. In the event of a job failure, this field is no longer updated and the date/time of the last update is displayed. This date/time can then be used to determine the reason for the failure.

When a job is started, the job starts a monitoring process in the same bshell in which it is running. This monitoring process sends job alerts and updates the Job Tick field every minute. If the bshell crashes, such as during a database failover, this field is no longer updated. After 60 minutes, the scheduled job's Status is set to Running Failure and the job's Status is set to Runtime error. The scheduled job is not deleted, and the last recorded job tick can be used to search the log and identify what went wrong.