Issue Management gives you a unified, organized view of integration failures, automatically categorizing issues and surfacing clear, business‑friendly insights so you can quickly understand what went wrong. It lists all open and closed issues along with key details such as status, category, and the number of impacted jobs and messages. The workflow includes:
- Identifying issues — filter the list, refine by time frame, and locate relevant items.
- Reviewing Issue Details — examine impacted Endpoints, Jobs, and Messages to understand scope and context.
- Using Guided Resolution (for supported issue types) — access root‑cause insights, recommended actions, and guided steps that help you resolve issues quickly without deep technical expertise.
- Changing issue status — apply updates and manage issue status as remediation progresses.
Identifying Issues
To identify issues, begin by accessing the Issues Page. The Issues page displays all issues, but only Current or Resolved at any given time. You cannot see both at the same time. See Filtering Criteria for more information about toggling between views of current and resolved issues.
Note: If your account is restricted to specific trading partners, the Issues page displays only Issues that contain one or more Messages associated with those partners. Issues without associated Messages do not appear because trading partner information is available only at the Message level. Users with access to all partners, including administrators, continue to see all Issues regardless of trading partner.
Each line on the Issues page contains information about an issue. Expand the table below for more details.
Issue information table
| Attribute | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Status |
The state of the issue. Possible status values are as follows:
|
||||||||||||
| Category | A classification that help organize, track, and resolve different kinds of issues. For more information, see Issue Categories. | ||||||||||||
| Issue | ID number and description of the issue. | ||||||||||||
| Impact - Endpoints | The name of the Endpoint impacted by this error. | ||||||||||||
| Impact - Jobs | The number of Jobs impacted by this error. Click to display the Jobs page filtered to display only these Jobs. | ||||||||||||
| Impact - Messages | The number of messages and the documents impacted by this error. Click to display the Messages page filtered to display only these Jobs. | ||||||||||||
| Occurrences - First | The first occurrence of this error. | ||||||||||||
| Occurrences - Last | The latest occurrence of this error. |
From here, you can filter or sort the list of issues or select one to view its details.
Filtering and Sorting the Issues List
To help you identify the issue you want to troubleshoot, you can narrow the scope of the data displayed on the Issue Management page through sorting and applying filtering criteria
Date Range
Select a date range to display messages that were sent in that range during that time.
You can choose a pre-defined date range or choose Custom Range to open a dialog box where you can specify a time and date range, including the time zone.
Note: When you select This week from the list of date ranges, the Messages page displays data starting from the current workweek -- that is, the previous Monday through the next Sunday. For example, if you selected This week on Wednesday, May 21, you would see data from Monday, May 19 through Sunday, May 25.
Note: All times and dates displayed in the Cockpit reflect the local time zone of the User's System unless otherwise noted using the Custom Range option - which means that you can select a different time zone for the same data. This can be useful when users across different time zones need to view the same data.
Note: The controls for this filter are located in the upper right corner of the page.
Sort List
Specify whether to sort on First or Last Occurrences column and toggle between ascending or descending sort direction.
Filtering Criteria
You can apply filtering criteria on the Issues page to narrow the scope of the data displayed.
You can toggle filters on the Issues displayed as follows:
| Filter | Description |
|---|---|
| Current or Resolved | Essentially, open or closed. Your selection controls the list of Issue Statuses you can choose from. You cannot view both Current and Resolved issues at the same time. |
| Status |
For Current Issues, choose from the following:
For Resolved Issues, choose from the following
See the Issue Information Table for more information about possible statuses. |
| Issue | The unique identifier for the Issue. |
| Endpoint | The name of the Endpoint associated with the issue |
| Document | Select one or more document types to restrict the display to only those document types. |
| Category | Select one or more issue types to restrict the display to only those types selected. See Issue Categories. |
| Partner | Select one or more trading partners to display only Issues that have one or more associated Messages for those partners. |
Reviewing Issue Details
Selecting an issue opens a detailed view for the issue. Alternatively, you can click the link in the Job or Messages column to display the Job or Message List page for the item in question, filtered for only the items relevant to the Issue you started with. See Working with Jobs and Working with Messages.
When you select an issue, a window appears containing details about that issue and a drop-down menu you can use to change the status of the issue. See Changing issue status.
The window contains three tabs discussed below.
Issue Tab
The top of the Issue tab contains links that display the Jobs and Messages pages, respectively, filtered for the Jobs or Messages impacted by the issue. See Working with Jobs and Working with Messages.
The remainder of the Issues tab contains detailed log information about the issue.
Summary Tab
The Summary tab contains information about the issue in an easy-to-understand format.
The information is displayed in the following sections:
- What Happened - Contains a detailed AI-generated summary of the issue based on the log information (displayed on the Issue tab).
- Recommended Action Plan - A plan you can implement to resolve the issue at hand.
Give us your feedback
Your feedback is important to us. Use the thumbs up or thumbs down buttons to share whether the resolution met your expectations.
Resolution & Recovery Tab
While the standard Summary tab offers general suggestions for resolving issues, Guided Resolution provides a dedicated Resolution & Recovery tab with detailed information, recommended fixes, direct links to apply those fixes, and options to recover the payloads affected by the issue. See Using Guided Resolution for more details.
Notifying your team
From the Resolution & Recovery tab, select Notify Team to open a dialog box for notifying your team or a trading partner about the issue. The modal is pre-populated by AI and fully editable before sending.
| Field | Description |
|---|---|
| Recipients | Enter one or more addresses in the To field. Select Cc/Bcc to reveal additional recipient fields. Addresses are validated as you type. |
| Message content | Subject, Body, and Signature are separate, AI-drafted, fully editable fields. Review and adjust the wording before sending. Nothing is sent until you select Send. |
| Attachments |
If the issue has one or more impacted messages, attachment checkboxes appear below Signature:
Selecting an attachment option automatically adds a description line above your signature. |
| Delivery tracking |
After you select Send, the modal reports one of the following statuses:
|
Recovering impacted payloads
Use the Recover Impacted Payloads section at the bottom of the Resolution & Recovery tab to retry or download the payloads affected by the issue. The number next to the heading is the number of impacted payloads.
The section has two tabs:
- Source Payload(s) or Target Payload(s) - Lists the impacted payloads with each payload's status, name, and Reported on date. The tab is named Source Payload(s) when the failure occurred before transformation and Target Payload(s) when it occurred after.
- Recovery History - Lists each recovery attempt for the issue. See Reviewing recovery history.
Retrying payloads
- On the Source Payload(s) or Target Payload(s) tab, select the payloads you want to recover. To select all of them, use the checkbox in the header row.
- Click Retry selected payloads.
CIC starts the recovery immediately. - In the Recovery Details dialog box, review the summary and optionally enter notes. Click OK to post the summary and your notes to the Discussion tab. Clicking OK doesn’t start or change the recovery.
CIC automatically determines the appropriate recovery method for each payload based on where the failure occurred, so you don't need to choose one. The exception is when the Data Flow originally used for a payload is unavailable. In that case, CIC asks you to select a different Data Flow before the Recovery Details dialog box appears. See Recovering payloads when the original Data Flow is unavailable.
After you submit the recovery, CIC adds an entry for each payload to the Recovery History tab with a status of Pending. The status updates automatically when the recovery finishes, so you don't need to refresh the page.
When all impacted payloads are recovered successfully, CIC automatically changes the issue status to Solved. For issues managed through Zendesk, CIC also updates the Zendesk ticket status and posts the recovery notes to the ticket as comments. If only some payloads recover, the issue status doesn’t change, and the Recovery History tab shows which payloads failed.
Note: Resolve the root cause of the issue before recovering payloads. Otherwise, recovered payloads may fail again.
Reviewing recovery history
The Recovery History tab lists each recovery attempt for the issue.
| Column | Description |
|---|---|
| Job | Link to the job for the recovery attempt. [verify: the job created by the retry] |
| Payload Name | The name of the payload that was retried. |
| Retried On | The date and time of the attempt. |
| Retried By | The user who started the recovery. |
| Status | Pending while the recovery is running. Failed or Successful when it finishes. [verify the exact success label] |
When a recovery attempt finishes as Failed or Successful, CIC also adds an entry to the Discussion tab with a summary of the job's results and a link to the job.
Downloading payloads
To download payloads for inspection, sharing, or archiving, select the payloads on the Target Payload(s) tab, then click Download selected payloads.
When you select a single payload, the file downloads directly. When you select multiple payloads, CIC emails a download link for a ZIP archive to the email address on your CIC user account. The ZIP file isn’t attached to the email.
Recovering payloads when the original Data Flow is unavailable
If the Data Flow originally used for a payload is missing or unavailable, CIC can't reprocess the payload using that Data Flow. This is common with Routing errors, where no Data Flow was found for the source and destination. When any payload you select is missing a Data Flow, CIC asks you to select one.
- On the Source Payload(s) or Target Payload(s) tab, select the payloads you want to recover.
- Click Retry selected payloads.
- In the dialog, select the Data Flow to process the payloads with and click Next. The dialog lists active Data Flows whose source is the Transformation endpoint. To find one, search by Data Flow name, source, or destination. CIC starts the recovery when you click Next.
- In the Recovery Details dialog box, review the summary and optionally enter notes. Click OK.
The Data Flow you select applies only to the payloads that were missing one. Payloads that already have a Data Flow keep it.
Discussion Tab
Use the Discussion tab to add comments, review past discussions, and collaborate with other users working on the same issue.
Self‑service vs. managed services issues
The Discussion tab behaves differently depending on how an issue is managed:
- Issues managed directly in CIC for self‑service customers include a running history of issue status changes in the Discussion tab.
- Issues created and managed through Zendesk, typically as part of managed services, use Zendesk as the system of record for status history. For those issues, the CIC Discussion tab does not show the same status change history, and status details should be reviewed directly in Zendesk.
The sections below describe how the Discussion tab works for issues managed directly in CIC.
Status history for self‑service issues
For issues managed directly in CIC, the Discussion tab shows a chronological history of issue status changes, making it easy to see how an issue progressed over time.
When an issue’s status changes, the update is automatically recorded in the Discussion tab with the previous status, the new status, who made the change, and a timestamp. This includes changes made to individual issues as well as updates performed through bulk actions.
Status categories
Issues managed in CIC fall into two high‑level status categories:
- Current — active issues such as New, Open, Pending, or On Hold
- Resolved — completed issues such as Solved or Closed
Status updates may occur within a category or when an issue moves from one category to the other.
What gets recorded
For issues managed directly in CIC, the Discussion tab records:
- Status changes within the same category (for example, New → Open)
- Status changes between categories (for example, Open → Solved), along with any comment you enter
- Status updates made through bulk actions, with each issue receiving its own entry
- System‑generated status updates, shown as distinct entries
- Notify Team send attempts: recipients, subject, and delivery status (Sent, Bounced, or Failed), with a follow-up entry if a bounce or failure is later resolved. Shown as a distinct, system-generated entry like other automated updates.
- Payload recovery: the summary note and any notes you enter in the Recovery Details dialog box, and the result of each recovery (Failed or Successful) with a link to the recovery job
User comments and system‑generated status updates appear together in time order. System entries are visually distinct so you can easily tell them apart from user comments.
Using Guided Resolution
Guided Resolution builds on Issue Management by taking you from understanding an issue to resolving it. For supported failure types, it provides root‑cause details, recommended actions, and guided steps to help you fix problems quickly without deep technical expertise.
Guided Resolution is supported only for certain issue types. See the following topics for more details about supported issue types:
Changing issue status
You can update an Issue’s status in two ways: from the Issues page or from Impacted Jobs or Messages
Changing status for a single issue on the Issues page
On the Issues page, select and open a single issue. On the Summary tab, use the drop-down menu to select a new status for the issue.
If there are open jobs or messages related to the issue, a confirmation dialog appears, allowing you to add a comment (visible on the Discussion tab) and proceed with the status change.
After completing the status change, a confirmation message appears.
-
On the Issues page, select the issues you want to close.
-
Click select "Close Issue" from the drop down menu.
-
In the Change Status dialog box, click Change Status.
Changing status from an impacted Job or Message
Open a Job or Message with an issue. You can do this from the Issues page by clicking the value in the Job column or Message column. Alternatively, you could open the impacted Job or Message from the Activity > Jobs or Activity > Messages page.
Either way, when you open the Job or Message, it displays with the Issue tab open. For example, if you open an impacted Job, a page like this appears.
Use the drop-down menu at the top right corner of the Issue tab to change the Issue's status.
Issue Categories
Issue categories in CIC Issue Management help ensure consistent handling of similar problems and support automation of alerting, ticketing, and escalations.
View Category Table
CIC Issue Management includes the following categories:
| Category | Description |
|---|---|
| API Failure | A failure in an API call — timeouts, invalid responses, or connectivity issues between CIC and an external system. |
| Authentication Error | Credentials are missing, expired, or incorrect, blocking access to an endpoint or service. |
| Business Process Failure | A business process fails to execute, typically due to logic errors, missing data, or misconfigured orchestration steps. |
| Connection Error | CIC cannot establish a connection to an external system at the network/transport layer — endpoint unavailable, network interruption, or no connectivity. (Failure to connect at all, before any transfer begins.) |
| Connector Error | A failure within a configured connector — misconfigured connector settings, unsupported operations, or runtime errors while interacting with an external system. |
| Database Failure | Data storage or retrieval fails due to database availability, connectivity, query execution, or data integrity issues. |
| Duplicate Interchanges | Identifies repeated EDI interchanges so they can be flagged or suppressed before duplicate processing occurs. |
| FA Rejected | A functional acknowledgement (FA) from a trading partner indicates a transmitted document was rejected — typically validation errors, format issues, or business rule violations. |
| File System Error | File or path operations fail at the endpoint — file/path not found, permission denied, write failures, or inaccessible directories. |
| Inbound Route Error | Incoming data cannot be matched to a defined inbound route, usually due to missing or incorrect routing configuration. |
| Mapping Failure | Data transformation breaks down — schema mismatches or invalid field mappings. |
| Miscellaneous | A catch-all for unclassified errors that don't map to a defined category. |
| Packaging Error | Occurs during AS2 message exchange when a transmitted message cannot be securely delivered or acknowledged — MDN signature/certificate-trust failures, remote-host MDN rejections (decryption-failed, authentication-failed, duplicate message ID, unexpected processing errors), and missing or timed-out MDNs. |
| Process Binding Not Found | A missing or broken link between a process and its expected execution context, such as a job or endpoint. |
| Protocol Error | A failure during execution of a transfer or message exchange over a communication-protocol endpoint (AS2, SFTP, HTTP). The connection or send operation does not complete — the transfer times out, is refused, returns an error response (e.g. 500/502/503), drops mid-stream, or the expected acknowledgement is never received. Distinct from configuration or data errors: the protocol-level exchange itself fails to complete. |
| Route Not Found | No route definition exists for outbound or internal delivery of a payload. |
| Routing Error | Occurs when CIC cannot resolve a transfer to a configured integration — no integration found for a given source/target endpoint (or endpoint + path) combination, a referenced endpoint ID that no longer exists, or an integration that exists but is disabled. |
Comments
0 comments
Please sign in to leave a comment.