The Payloads View in CIC streamlines payload management by allowing users to search and filter payloads across jobs and/or within a time range, resend only the necessary ones, and monitor retry status through visual indicators. These capabilities help resolve issues faster, reduce manual effort, and eliminate the need to reprocess entire jobs.
The Activity > Payloads page displays a list of payloads, with key details shown in the main panel and filtering options available in the left column. Users can view job-level and payload-specific information (see Viewing Job Details and Understanding Payload Details), as well as apply filters to narrow down the displayed results (see Filtering Payload Activity).
Currently, the Payloads View displays only target payloads—those being delivered to their final destination via CIC Agent or standard protocols like AS2 or SFTP. Source payloads, which enter transformation processes before delivery, are not included. Additionally, payloads generated by API calls are not shown in this view.
Viewing the Payload List
The Payload List provides a centralized view of all processed payloads, making it easy to inspect delivery details, monitor statuses, and apply filters to narrow down results. This helps users quickly locate and act on specific payloads without having to dig through entire jobs.
-
Go to Activity > Payloads.
-
The first time you open this page during a session, you must do one of the following to display Payload data:
- specify a date range
- specify filtering criteria
- click the Apply current date range button.
-
The list of Payloads for that date range and/or filter criteria is displayed.
Each payload displays a set of attributes, some of which can also be used as filtering criteria to narrow down the list.
| Attribute | Description | Available as Filtering Criteria |
|---|---|---|
| Status |
Status of Payload processing. Possible values are:
|
Yes |
| Payload | Name of the payload file. | Yes |
| Size | Size of the Payload file in KB. | No |
| Job | Payloads associated with this Job. Click the job number to open the Job Details page for that Job. See Working with Jobs. | Yes |
| From | Source Endpoint. | Yes |
| To | Destination Endpoint. | Yes |
| Time | The time the payload was generated. | Yes (as part of a date range) |
Filtering Payload Activity
Use the filtering options in the Payloads View to quickly narrow down results based on criteria like date, status, or endpoint, making it easier to locate and act on specific payloads.
Choose from the following filtering criteria.
| Filter | Description |
|---|---|
| Status |
Status of Payload processing. Possible values are:
|
| From | Source Endpoint. You can browse a list of Endpoints or type in the name of an Endpoint. |
| To | Target Endpoint. You can browse a list of Endpoints or type in the name of an Endpoint. |
| Payload Name | The exact or wildcarded Target Payload file name. Use the * (asterisk) for wildcard searches. |
| Job | The number of the Job associated with the Payload. |
| Issue | The ID of the issue associated with the Payload. |
Next steps:
- Click a Job related to a Payload to see Job details. See Working with Jobs
- Select one or more payloads and click the Resubmit button. See Resubmitting Payloads
Viewing related Job details
Each payload is linked to a job, and viewing the related job details provides valuable context about the broader transaction—such as processing steps, partner information, and overall job status. To access this information, click the value in the Job column for any given payload. For more details, see Working with Jobs.
About Resubmitting Payloads
When a Payload fails or requires reprocessing, CIC enables users to manually resubmit it—ensuring accurate delivery without restarting the entire job.
Note: Resubmitting Payloads is only supported when the Data Flow and Endpoints from the original transfer are still available. If either of the original Data Flow or Endpoint is missing, the Payload cannot be resubmitted.
There are two use cases for resubmitting payloads: retry and resend.
A retry is an attempt to re-deliver a failed payload without initiating a new job. Failures may occur due to transient issues, such as network interruptions or unavailable Endpoints. By default, retries are triggered automatically—see Retrying Failed File Transfer Attempts. You can also manually trigger a retry from the Payload page. Retries are part of the original job: if successful, the job status updates to reflect success; if not, it remains marked as failed.
A resend is a manual action that creates a new job to reprocess a previously successful payload. It’s typically used when the original job has completed successfully, and a resend is needed due to a trading partner request or changes to business logic.
Resubmitting Payloads
The following steps guide you through the process of initiating a resubmission to ensure successful delivery.
- On the Payloads page, locate the payloads you want to resubmit. See Filtering Payload Activity.
-
Select the checkbox for each payload you want to resubmit and click the Resubmit button.
Comments
0 comments
Please sign in to leave a comment.