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
You can toggle filters on the Jobs displayed as follows:
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.|
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.
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.|
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.
|Current||Indicates the issue is current (unresolved). Note that some jobs can be resent from the point of failure after the 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 Job Detail page appears and displays information about that Job.page, the
Job details contain several types of information:
- Data Flow
The Job Detail page shows Data Flow information for the Job. Click the name of the Data Flow to display it on the Data Flow edit page.
The Payload tab lists the files transferred as part of the job. Each payload listed is a download link.
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.
Whether or not the Jobs page can display it, you can download the request body.
When a Job has an error associated with it, the Issue tab is displayed for the Job step where the error occurred and the 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
- Select failed inbound or outbound job to retry.
- Click the Job Retry button.
- Refresh your browser.
- 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.