By default, the Activity > Jobs page displays a list of the most recent Jobs. The main part of the page contains information about your Jobs (see Viewing Job Details and Understanding Job Details ) and the left column contains some controls for filtering the Jobs displayed (see Filtering Job Activity).

Click the job number in a line item to see detailed information about that Job. See Viewing Job Details.

Filtering Job Activity

You can apply filtering criteria on the Activity > Jobs page.

You can toggle filters on the Jobs displayed as follows:

Filter	Description
Date Range	Jobs run during the range you select.
From	Jobs that include the source Endpoint you specify. You can type in a value or click Browse to select from a list.
To	Jobs that include the destination Endpoint you select. You can type in a value or click Browse to select from a list.
Payload Name	Jobs that include a payload with the name you specify. Partial payload names can be specified in this field in conjunction with the asterisk (*) or question mark (?) wildcard characters.  Use an asterisk (*) to represent any number of characters, and a question mark (?) to represent a single character. For example: a*z would return az, abcdz and so on. a?z would return abz, acz and so on.
Status	Jobs with the status you select. See Job Status for more information.
Job	Job with the job number you specify. You can specify partial values and use wildcards in this field.

Job Status 

The Job Status can be successful, in progress, or failed due to an issue. If the Job has an issue associated with it, the Job status indicates whether it is a current (unresolved) issue or a resolved issue.  

Note: The statuses described below relate to how the job statuses are currently used to coordinate between Cleo and Cleo Managed Services customers.

Icon	Category	Description
	Current	Indicates the issue is current (unresolved).  Note that some jobs can be resent from the point of failure after an issue has been resolved.  This category contains four sub-categories
	Open	Issue has been assigned to Cleo and action is pending from Cleo.
	New	Issue has not been assigned to anyone yet.
	Pending	Issue requires assistance from you, the Cleo customer.
	On Hold	Issue requires assistance from your Partner.
	Resolved	Indicates a Resolved issue.
	Solved	Issue is solved, but not closed. Issues are closed after 3 days of being marked as Solved.
	Closed	Issue is closed.

Updating Job Issue Status

Self-service implementation users can update the status of an issue from the Issue tab on the Job Details page. 

Viewing Job Details

When you click on a Job on the Activity > Jobs page, the Job Detail page appears and displays information about each step in that Job.

Click on a step to drill down into details about that step. By default, the first step in the Job is highlighted and details for that step are displayed.

When you select a Destination Job step that has more than one destination Endpoint, those destinations are listed separately; they are listed on the left side of the page. Click one of those destinations to display details about the job for that destination. The same collection of data (that is, messages, payloads, logs, and so on) is displayed for each of the destinations in a Job step.

Understanding Job Details 

Job details contain several types of information: 

• Data Flow
• Payload
• Message
• Log
• Issue 

Data Flow

For Job steps with Endpoint types other than API, Application Connector, and Database, the Job Detail page shows Data Flow information for the currently selected Job step. Click the name of the Data Flow to display it on the Data Flow edit page. 

API, Application Connector, and Database Endpoints do not use Data Flows.

Payload

The Payload tab lists the files transferred as part of the job step in question. Each payload listed is a download link. If there are any EDI messages associated with a payload, a link to the Messages page is displayed on the Payload tab. 

Log

The Log tab shows a list of events generated by CIC during the job. For each event, the list includes a timestamp, a success/failure icon, name of the event, and an informational message about the event. 

In steps where there are API or Application Connector Endpoints, the events listed are expandable. Expanding an event shows the associated request headers and body. You can expand the headers to see those details. The body is displayed automatically if the content-type is 'application/json', 'application/ld+json', 'application/vnd.api+json', 'application/xml', text/csv', 'text/plain', or 'text/xml'.

Whether or not the Jobs page can display it, you can download the request body.

When you click the Transformation step, the Log tab displays a list of Events with associated Timestamps and Messages. The Messages column contains an execution number and information about the Business Process associated with the execution number. This execution number also corresponds to an entry in the Auditor Log

Message

The Messages tab shows the EDI messages generated for the job. The Messages tab is typically associated with the Transformation step or the Destination step when the destination is an API endpoint. Each Message listed is a link to the Activity > Messages page.  

Issue

When a Job has an error associated with it, the Issue tab is displayed for the Job step where the error occurred and the message or log entry that has an error is marked.

Resending Failed Jobs with the Retry Job button

Sometimes when sending a job to its destination, a failure may occur due to permission or storage issues, etc. Once the issue gets corrected, you can quickly resend the job from exactly where it failed using the  Retry Job button, which displays at the top right corner of the Job Detail page when certain failures occur.

Not all jobs can be retried with this option. However, the Retry Job button only appears when a job can be.

How it works

In Summary:

1. Select failed inbound or outbound job to retry.
2. Click the Retry Job button.
3. Refresh your browser.
4. View the results.

In the simple example below we see that a job has failed and an Issue has been created.

You can check the Payloads tab to see details of the issue, and also the Log tab to see the events, which in this example, shows a SEND_FAILURE.

After troubleshooting and correcting the problem, you would click the Retry Job button. This results in the job being queued for retry.  Important: At this time, users must refresh their browser in order to see the outcome of the retry.

Once complete (and issues addressed), the Job Detail page displays the job as successful. 

You can also confirm this in the Payloads and Log tabs (shown here). Note that the SEND_FAILURE, as well as MANUAL_RETRY, have been logged.

Resending failed Jobs that contain multiple payloads and job steps

Failed jobs that contain multiple payloads and multiple job steps can also be retried using the Retry Job button. In this example, two of the five job steps have failures. Once the issues have been resolved, clicking the button would retry the failed job steps. Note that not all jobs can be retried with this option. However, the Retry Job button only appears when a job can be.

A successful run of these job steps would then display.