The Errors page opens whenever you select the error count on a flow step, and it works like a dedicated workspace for locating, analyzing, and resolving errors — individually or as a team. This article covers what's on the page and what each part means, so Retry or resolve flow errors, Tag errors, and Assign errors can focus on actions instead of re-explaining the layout.
A single page displays up to 1,000 errors at a time, and a full error list across pages holds up to 20,000. Search, sort, and filter operations apply to the entire list across pages, not just the page you're viewing.
Prerequisites:
- Account permissions — You need Monitor All or Manage All permissions to view the Errors page. An account admin can grant Monitor users permission to edit retry data, or to invite and assign errors to new users.
- Environment — If your account has multiple environments, make sure you're signed in to the correct one (production or non-production) before you look for errors — errors don't cross environments.
The three tabs
| Tab | What it shows |
|---|---|
| Open errors | Unresolved errors that need review, a data edit, or a manual retry. This is the tab that opens by default. |
| Resolved errors | A historical log of errors resolved either automatically (Auto-resolved) or by a person (User-resolved). Auto-resolution is turned on by default for new flows and connections, and typically resolves rate-limit errors and intermittent or repeated errors. |
| Retries | The status and details of retry attempts currently in progress or recently completed, whether you triggered them manually or auto-resolve triggered them. |
Open errors tab layout
The Open errors tab opens in a split-screen view — an error list on one side and error details on the other — with the Hide error details panel icon at the top right of the modal to hide or show the details pane if you want to see more of the list.
The tab supports:
- Individual or collaborative resolution — work through errors yourself, or use tags and assignment to divide the work across a team.
- Celigo Ora, an AI assistant you can prompt for guidance on a specific error, and that can stage retry data fixes across a flow step's errors. See Error management with Celigo Ora.
- Trace key tracking — the unique identifier for a record, visible as a column in the list and at the top of an error's details. See Set a custom trace key to uniquely identify a record.
- Column and layout controls — show, hide, reorder, and resize columns, and adjust the split between the list and the details pane; your layout preferences persist across sessions.
- Editing retry data in place — a blue dot next to an error's checkbox indicates its retry data was edited but not yet retried.
- Downloading errors for offline review or audit.
- A slider for browsing through the error list without leaving the details view.
Error list columns
| Column | Description |
|---|---|
| Timestamp | When the error occurred. Sorts ascending or descending (descending — most recent first — by default). This is the only sortable column. |
| Message | The specific error description and any API payload details that help guide resolution. |
| Celigo Ora | Entry point to prompt the AI assistant for troubleshooting guidance on that error. |
| Classification | The categorized error type (see Error classifications) that hints at the fix. |
| Code | The technical error code returned by the application or by integrator.io. |
| Source | The flow component that produced the error — for example, a filter, script, or lookup, or the name of the external application. |
| Assign | The user currently assigned to resolve the error. |
| Tag | Any custom labels applied for filtering or prioritization. |
| Trace key | The user-defined unique identifier mapping the error to a source record. |
| Error ID | The error's unique ID. Hidden by default; select it in the column display settings to show it. |
Timestamp and Message always stay visible in the table to anchor the context for every row, even if you hide other columns.
Error details fields
Selecting an error opens its details. Only the retry data is editable — everything else is there to help you diagnose the problem.
| Field | Description |
|---|---|
| Retry data | The editable source data payload. Change values here before running a retry — for example, correcting a malformed phone number. |
| Fields | A read-only set of core metadata: message, code, source, timestamp, error ID, and classification. |
| Request | The raw headers, URI path, and body sent to the destination endpoint. Available for HTTP, NetSuite, and Salesforce steps. |
| Response | The raw payload, error codes, and status messages returned by the destination application. Available for the same step types as Request. |
If a trace key is defined for the error, it appears at the top of this panel.
Customize the column display
- Show or hide columns: select the Column configuration icon at the top right of the list, check or uncheck fields, then select Apply (Reset restores the defaults). Timestamp and Message can't be hidden.
- Reorder or resize: drag column headers to reposition them, or drag a column border to change its width.
Filter, search, and sort
- Filter by Source, Classification, Assign, or Tag, including filtering for errors with no value in a given field. Clear a filter by unchecking its box.
- Search the entire list — not just the current page — by keyword, within a filtered subset or across all open errors.
- Sort by selecting the Timestamp column header to toggle between ascending and descending order.
Retries tab reference
The Retries tab shows the progress and outcome of retry runs, whether triggered manually from Open errors or automatically by auto-resolve.
| Field | Description |
|---|---|
| Retry status | Completed (green) — the retry succeeded with no errors. Completed (yellow) — the retry finished but produced errors. Canceled (gray) — the retry was stopped before finishing. |
| Duration | The time the retry took to complete. |
| Retry started and Retry completed | Timestamps for when the retry run began and ended, shown in your profile's date/time format. |
| Success | The number of errors successfully retried. |
| Ignored | The number of errors ignored during the retry. |
| Errors | The number of open errors remaining from the run. Not clickable — if a retry in one step triggers an error in the next step, that count shows on the next flow step instead. |
| Retry started by | The user who started the retry, or Auto-retried for retries triggered by auto-resolve. Filterable; defaults to showing all users. |
|
Actions |
Lets you cancel a retry that's still in progress. Canceling stops any errors not yet processed; errors already processed keep their current state. |
While a retry runs, a Retrying errors message appears at the top of both the Errors page and Flow builder; it changes to Retry completed when the run finishes. Select View Results to switch between the two views. If you retried errors in more than one step, select a step from the drop-down at the top to see that step's results.
You can view the same retry details from the Run console or Run history in Flow builder. For the cancel-a-retry procedure, see Retry or resolve flow errors.