Error: The Workflow Becomes "Stuck" in fico

Cause

During job scheduling using the workflow, if an error occurs in the program section of the report and the report is being run at the AT SELECTION-SCREEN OUTPUT event, then the job is not scheduled.

Error Handling

The system issues an error message to notify you that scheduling is not complete.

The message is linked to a user decision. This message is sent as a top priority mail to the person whose name is entered in the detail screen for maintenance of jobs in the flow definition, in the When error, mail to section (see also: Creating a Flow Definition). That person receives the message in their mail inbox.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

• You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
• You executed the transaction online.
• You decided that the error is not relevant.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

Error: The Workflow Stops in fico

Cause

The workflow stops due to an error in the workflow runtime system.

Symptom

The job just scheduled is completed since the job control functions separately from the workflow. However, the following steps in the flow definition are no longer executed.

Error Handling

It is not possible to restart at the point where the workflow stopped. Therefore, you need to reschedule the whole flow definition.

Error: Job Scheduling Was Unsuccessful in fico

Cause

Scheduling a job can be unsuccessful if the technical name of the report or variant was changed after the flow definition was created. This means that the technical names in the flow definition no longer exist.

Error Handling

The workflow recognizes the error and issues an error message displaying the faulty technical name of the report or variant.

The message is linked to a user decision. This message is sent as a top priority mail to the person whose name is entered in the detail screen for maintenance of jobs in the flow definition, in the When error, mail to section (see also: Creating a Flow Definition). That person receives the message in their mail inbox.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

• You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
• You executed the transaction online.
• You decided that the error is not relevant.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

Error: An Executed Report Found an Error in fico

Symptom

Due to an error in the content, the REPORTERROR workflow event was triggered.

Error Handling

The workflow executes an error dialog. This contains a user decision. The user decision is sent as a top priority mail to the person whose name is entered in the detail screen for maintenance of jobs in the flow definition, in the When error, send to section (See also: Creating a Flow Definition). That person receives the mail that an error has occurred in program X, variant Y in their mail inbox.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

• You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
• You executed the transaction online.
• You decided that the error is not relevant.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

No user decision is called up for jobs that have worklists. This is because the error handling for worklists is triggered by rerunning the task steps in the workflow. Therefore, programs written for worklists always trigger the FINISHED event.

Graphical Representation of the Flow

Error: A Job Becomes "Stuck" in fico

Symptom

The program has a runtime that is far longer than expected.

Error Handling

The dialog for a processing error in the program is handled in its own sub-workflow. which consists of a user decision. This message is sent as a top priority mail to the person whose name is entered in the detail screen for maintenance of jobs in the flow definition, in the When error, mail to section (see also: Creating a Flow Definition). That person receives the mail that an error has occurred in program X, variant Y in their mail inbox.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

• You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
• You executed the transaction online.
• You decided that the error is not relevant.

You can use this option for jobs that have worklists. However, you need the worklist ID to be able to execute the job outside of the workflow.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

Graphical Representation of the Flow

Error: A Job Stops

Cause

The job stops, if for example, the system is turned off.

Error Handling

The dialog for an error in the job administration is handled in its own sub-workflow, which consists of a user decision. This message is sent as a top priority mail to the person whose name is entered in the detail screen for maintenance of jobs in the flow definition, in the When error, mail to section (see also: Creating a Flow Definition). That person receives the mail that an error has occurred in job XY in their mail inbox.

There are two options in the user decision.

Continue the flow with the next task

You choose this option if:

• You corrected the error and rescheduled the job manually in a separate session, and are waiting for the job to be executed.
• You executed the transaction online.
• You decided that the error is not relevant.

You can use this option without any problems, for jobs that have worklists. However, you need the worklist ID to be able to execute the job outside of the workflow.

Reschedule the job

You choose this option if you corrected the error and would like to use the Schedule Manager to control the rescheduling of the job.

Graphical Representation of the Flow

Error Handling

Job error handling involves the following:

1. For checking purposes:

• Periodically reading the job status
• Checking the maximum runtime

2. When errors occur:

• User decision "Continue the flow with the next task"
• User decision "Reschedule the job"

The user decision "Reschedule job" is not available for worklists.