Scheduler on RIA Docs

Jobs Activity

Mon, 01 Jan 0001 00:00:00 +0000

The Job Activity module displays the status and history of executed jobs, including completed, failed and running jobs.

Field	Description
Job Name	Name of the job. The Job Name link allows you to view the job details.
Start Date	Date and time when the job was executed.
Next Run	Date and time when the job will be executed again.
Duration	Total time taken for job execution.
Chain	Specifies the chain associated with the job.
Step	Specifies the step associated with the job.
Status	Status of the job activity. The following are the possible values: `Running` `Chain Stalled` `Scheduled` `Completed` `Failed` `Stopped` `Disabled`
Action	Displays the following icons: Run Log History — Opens execution logs for the job. Activate Job — Allows you to rerun the job.

Job Summary

The Run Status Job Summary provides a summary of the current status of all job executions. To view it, click the Go to Job run summaryicon.

Task Flow

Mon, 01 Jan 0001 00:00:00 +0000

Overview

A task flow is a configurable sequence of steps that defines how tasks are executed within the system. Each step in the flow represents either an individual conversion task or another task flow, allowing you to build a simple or multi-level workflows. This module also allows you to link steps together and define rules.

When a task flow is selected, the page is divided into the following sections:

Job

Mon, 01 Jan 0001 00:00:00 +0000

Overview

A job is a task that runs within the system. It is linked to chain for execution. The conversion tool tracks the execution of a job and creates the status tree from the job and chain information.

Create or view a job

When creating or viewing a job, the Job Details and Notifications are displayed.

A newly created job will always be disabled the first time.

Job Details

Job Details provide information about a specific job, including its name, sender, recipients, and relevant parameters.

Schedule

Mon, 01 Jan 0001 00:00:00 +0000

Overview

A schedule defines when a job should run, either as a one-time execution or as a recurring execution. By associating a schedule with a job, the system can automatically trigger execution based on the defined timing and frequency. This helps ensure consistency, reduces manual intervention, and supports time-based automation of processes.

Creat a schedule

When creating or viewing a schedule, the following fields need to be filled out or displayed, respectively. To create a new schedule, click the Create New button.

Run Status

Mon, 01 Jan 0001 00:00:00 +0000

The Run Status displays the run status of a job. A job is a collection of tasks created by the user to carry out various operations in DIH.

Once a job is called out for execution, it starts executing the tasks within that job. The execution summary of the tasks within the job is stored in the Run Status - Job Summary page. This page consists of a list of all the jobs displayed in the following format:

Error Management

Mon, 01 Jan 0001 00:00:00 +0000

When a job encounters an error or is cancelled, it can behave in two ways:

Stalled (default) — The job remains active in the scheduler but pauses due to the error.
Stopped — The job fully stops execution.

This behavior depends on the the ria-boot.properties com.ria.converter.stopJobOnError property, or the stopJobOnError Task parameter:

false — the job becomes stalled, which is the default and recommended setting
true — the job will be stopped.

The stalled approach is newer and preferred because it allows easier troubleshooting and restarting, though the stopped option is available for backward compatibility.

Stalled jobs

By default, a failed task causes its job to enter a stalled state and appear under the Stalled Chain group in the Jobs Activity page. Although the run status may show the job as ended with an error, it is still considered running by the Oracle DBMS Scheduler and can be verified through the ALL_SCHEDULER_RUNNING_CHAINS view. To avoid unnecessary resource usage, the issue should be resolved and the job restarted, or the job should be stopped, with the option to restart it later.