The Errors page is available when errors occur within any flow steps in the Celigo platform (integrator.io). Clicking the errors/error count in a flow step opens the Error page that's like a workspace enabling you to quickly and easily locate, analyze, and resolve the errors, individually or collaboratively. You can use this page to fix data payloads, manage error assignments, categorize issues with tags, or execute batch/bulk retry operations.
A single page shows a maximum of 1,000 errors at a time, and an entire list across pages is a maximum of 20,000 errors. When you search, sort, or filter errors, the operation is performed for the entire list across pages, rather than for a single page.
Before managing flow errors, ensure you meet the following requirements:
-
Account permissions: You must have a minimum permission tier of Monitor All or Manage All to view the Errors page. The Admin must grant Monitor users, permissions to edit retry data, or invite and assign errors to new users.
-
Environment: If you have multiple environments, ensure you are signed in to the correct environment (Production or Non-production) to view and retry/resolve errors.
The Errors page organizes your troubleshooting workflow into three dedicated operational tabs.
|
Tab |
Description |
|
Open errors |
Displays unresolved errors that require review, data edits, or manual retries. This article focuses on fixing unresolved open errors from the Open erros tab. |
|
Resolved errors |
Displays a historical log of both auto-resolved and user-resolved errors. You can automatically or manually resolve errors. Automatically resolved errors show as auto resolved, and manually resolved errors show as user resolved. The UI settings for automatic error resolution are enabled, by default, and typically manage the following errors:
|
|
Retries |
Shows the status and details of current retry attempts. For more information, see Monitor and manage retries. |
The Open errors tab opens by default and enables you to perform several actions to effectively troubleshoot errors.
-
View errors, & quickly examine related details in the same context.
-
Drag the button in the page to maximize or minimize a section.
-
Browse through the error list by using the slider beside the errors.
-
Change the layout to easily examine details or perform any action.
-
Edit the retry data within the same context, as required, before you retry any errors. (You can then later make a change in the source application.)
-
View the trace key, if available, that's a unique identifier to locate or check records in the source/destination applications.The trace key is easily visbile as column in the errors list and also shown at the top of the errors list
-
Download all errors or errors for a specific period for audit purposes or to analyze them offline.
-
View the open errors, resolved errors, or retries when fixing errors.
-
Select a single, several, or all errors to retry or resolve them quickly.
-
Sort errors by the timestamp column; or, filter errors in columns, where applicable, to examine and detect patterns.
-
Add tags to categorize or prioritize errors.
-
Assign errors to users to resolve them collaboratively.
When you retry errors, you can view the status and the results at the top of the page.
The Open errors tab opens by default.with a split-screen view of the errors list and details. But, you can click the button at the top to hide (or show) the error details and better view the error list.
1 - assign/tag errors for self/collaboration, 2 - Celigo Ora (AI), 3 - Trace key tracking, 4, 5, 6 - Refined data display (4 - show/hide columns, 5 - filter, 6 - search) , 7 – Flexible layout, 8 – Quick navigation, 9 – Edit retry data
The Open errors tab supports the following key features:
-
Individual/Collaborative error management: Retry or resolve errors by yourself, or use tags & assignment within your team to resolve errors .
-
AI-powered troubleshooting: Prompt Celigo Orra and get guidance to retry and resolve errors.
-
Trace key tracking: Locate records via the unique identifier displayed as a column in the Errors list, or at the top of the Error details panel.
-
Refined data displays: Show/hide, sort, search, or filter columns to analyze and manage errors. You can resize sections or columns.
-
Flexible layouts: Adjust the split-screen layout (Error list & Error details) to examine specific payloads or match your operational workflow. You can reorder, resize, or alter the visibility of columns to streamline your troubleshooting view:
-
Quick navigation: Browse the error list by using a slider beside the errors.
-
Edit retry data within the same context: Edit the retry data within the same context and test if the error is resolved ater you retry it. When retry data is edited by anyone on the team but not retried, it's shown by a blue dot on the box next to any errors in the list.
-
Download errors: Download errors, when required, for collaboration, analysis, or compliance.
For more details to manually resolve errors, see the Error list and Error details sections that follow.
The Error list shows all processing failures for the selected flow step with the timestamp, message, code, source, classification that provide hints or clues to correct your errors. You can retry or resolve a single, several, or all errors quickly from the Error list using the action buttons at the bottom of the list.
You can click the Refresh errors button at the top to see the latest changes for open errors. When examining error details, click the button at the top to customize the table layout and view only the error list.
|
Column |
Description |
|---|---|
|
Timestamp |
Shows the most recent errors based on the time of occurrence. You can sort the errors in ascending or descending order (default). |
|
Message |
Provides the specific error description and API payload messages to guide resolution. |
|
Celigo Ora |
Celigo Ora, the AI-assistant, is also available to troubleshoot errors based on the clear prompts you provide. You can disable Celigo Ora, if required. |
|
Classification |
Displays the categorized error type (such as |
|
Code |
Provides the technical error code returned by the application or platform runtime. |
|
Source |
Indicates the flow component causing the error, such as filters, scripts, or lookups. |
|
Assign |
Displays the account user (avator icon), designated to resolve the error. |
|
Tag |
Displays the custom labels applied to the error for filtering and prioritization. |
|
Trace key |
Displays the user-defined unique identifier that maps the error to a source record. |
|
Error ID |
Select the column to view it in the table (hidden by default). Displays the unique ID of the error, that's also shown under Fields in the Error details. |
The Error details panel displays the rich technical context of a selected error row. Only the Retry data is editable, the other settings provide details that might help to troubleshoot errors.
Error details have the following common fields that you can carefully consider, make changes to the retry data, and correct the errors. If the trace key is defined, then it's shown at the top of this section.
|
Field |
Description |
Example |
|---|---|---|
|
Retry data |
An editable setting containing the source data payload. You can modify these values before running a retry. |
For example, edit an incorrect phone number 123-456-7890 |
|
Fields |
A structured definition list displaying standard core platform metadata. |
For example, Message: {"error": "SupportProductInactive", "description": "You must have a valid Support account to call this API"} Code: 403 Source: Zendesk Support Timestamp: 2022-10-11T14:17:21.589Z Error ID: 6526483935 Classification: Value |
|
Request |
Displays the raw headers, URI path, and body sent to the destination endpoint. Available for HTTP, NetSuite, and Salesforce steps. For any related details, see the HTTP universal connector, NetSuite, & Salesforce sections. |
GET https://api.zendesk.com/v2/users/123 |
|
Response |
Displays the raw payload, error codes, and status messages returned from the application. Available for HTTP, NetSuite, and Salesforce steps. For any related details, see the HTTP universal connector, NetSuite, & Salesforce section. |
{"error": "Forbidden", "description": "Valid account required"} |
Click Retry or Resolve to act on a single error.
When you click Celigo Ora for an error, it receives error details, flow context, recent flow modifications, error patterns within flow step, and relevant Celigo info that is public to tailor a response without you having to gather or paste input. This guidance could save you time and effort in resolving errors. You can also provide your feedback to responses by clicking the thumbs up or down to show your satisfaction with the Celigo Ora help.
You can decide on the visibility, order, or size of columns to streamline your troubleshooting view.
-
Show or hide columns: Click the column show/hide button, and then check or uncheck the boxes next to the fields based on the table view you require. The Error ID is field that is hidden by default. Timestamp and Message are fields that always remain in the table to anchor the context for errors.
-
Reorder or resize: Drag and drop column headers to reposition them. Hold and drag the column borders to adjust widths. Form fields adapt automatically to minimize horizontal scrolling.
-
Filter errors: Select the filters to isolate records by Source, Classification, Assign, or Tag. For example, select
Valueunder the classification filter to display data errors. Uncheck the boxes to clear active filters. Filters also support empty data states such as blank classifications. -
Search the entire list: Enter keywords in the search bar to find specific error strings within a filtered subset or across all open errors.
-
Sort rows: Select the timestamp column to change the sorting order. Sorting is only supported for timestamp, users can view the most recent or oldest error.
Collaborate with team members to resolve issues by categorizing or delegating errors, or tagging/assigning errors to yourself if you're a lone team member. The tags and assignment can helps others to be informed about the status or action on any errors.
-
Apply tags: Select an error, and then enter a label to categorize or prioritize the issue. You can filter by these custom tags later.
-
Assign owners: Select an error row, and then select a team member from the Assign dropdown to delegate resolution tasks.
You can modify data and re-run failed records individually, process them as a batch page, or execute bulk updates across the entire error list for the flow step.
-
Go to the account or integration Dashboard and click the error count.
-
In the Open errors tab of a flow step, check the box next to an error in the list.The row gets highlighted.
-
To retry the error, review the error and payload details (or, if required, consider other tools to investigate the error) and then, as required, edit the retry data in the Error details or Error list section. If you or a team member save the retry data, it's saved across sessions, and if the retry data is edited but not retried, you'll see a blue dot next to to the error checkbox.
-
In Error details, click Retry to fix the error. Or, click Resolve to dismiss the error.
You can view the progress of the Retry operation at the top of the page. When you click the Retries tab at the top of the page, it provides details of your run.
-
Go to the account or integration Dashboard and click the error count.
-
In the Open errors tab of a flow step, you can use filters and quickly select mutiple errors or Select All to quickly select all errors (max. 1,000 records) on the page. Select all checks all boxes on a page, regardless of any filters or search.
-
To retry the error, review the error and payload details (or, if required, consider other tools to investigate the error) and then, as required, edit the retry data in the Error details section.
-
Click Retry to fix the errors. Or, click Resolve to dismiss the errors.
When you have a large list of errors, you can choose to:
-
batch retry – select all and Retry the open errors shown on the current page up to a maximum limit of 1,000 errors (batch retry), or
-
bulk retry – select all and Retry all the open errors in the entire list across pages up to a maximum limit of 20,000 errors
Based on the button you click, action is taken in one-go on a single page or several pages of errors, ignoring any filters or search applied. Keep in mind that clicking Retry All or Resolve All automatically selects all errors across pages, including pages that you are not currently viewing.
To batch/bulk retry or resolve all errors in the entire list:
-
Go to the account or integration Dashboard, and click the error count.
-
In the Open errors tab of a flow step, check the box next to Select all.
-
Based on your requirements,
-
Batch retry: If you want to retry all errors on a single page, click Retry, or if you want to dismiss them, click Resolve.
-
Bulk retry: If you want to retry all errors across pages, click Manage all > Retry All, if you want to dismiss them, click Manage all > Resolve all.
The number of errors to retry or resolve are shown on the retry and resolve buttons at the bottom of the page. Also, you can see the number of errors at the top of the page in Results.
-
Downloading your errors can sometimes make it easier for you to identify patterns or work through them carefully or collaboratively offline.
To download your Error list:
-
Go to the account or integration Dashboard and click the error count.
-
In the Open errors tab, click the Download button in the top-right corner.
-
In the Download errors page, select the From and To dates for a specific period, or Download All.
-
If you selected a specific period, click Download.
The file with the error fields is downloaded in your default location.