Explore the integration dashboard

The integration dashboard shows you the status of every flow that ran for the last 30 days or however long your data retention plan allows. From here you can watch your flows run in real-time, review errors as they occur, and review your run times. The dashboard has two tabs: Running flows and Completed flows.

Integration dashboard

Contents

• Running flows
  • Flow status
  • Errors
  • Pages (pagination)
• Completed flows
  • Errors
    • Open errors
    • Resolved errors
  • Runs
  • Pages (pagination)

Running flows

You can see any currently running or queued flows from this tab and review any real-time errors. For larger integrations, you can filter by flow name and status.

Running flows

Flow status

When a flow runs, integrator.io creates a set of jobs to complete the tasks configured at each flow step. These jobs are stacked in a processing queue until the flow is complete. If a flow is scheduled to run while one or more of its connections are still in use by another active flow, the Dashboard tab displays the message, Waiting in queue next to the flow awaiting processing. integrator.io finishes the active flow before moving on to the next flow in the queue.

When flows are processing, the Status column displays an In progress message. You can click the message in the Status column to open the Queued jobs window. From here you can view all flows and associated messages currently processing (or queued to run) and cancel jobs in progress.

The Started column displays the timestamp for your flow’s latest run. You can configure your account profile to display timestamps in any date/time format. If you’ve set your account to relative time, the timestamp is displayed as the length of time between the started date and time and the current date and time (1 day ago, 3 hours ago).

The Success and Ignored columns display the number of successful and any ignored records.

You can also cancel a running flow using the Actions overflow menu.

Errors

There’s a live count of accumulating errors and auto-resolved errors. integrator.io auto-resolves errors by using trace keys to find and resolve duplicate errors. The trace key is the unique identifier of a record, as determined by integrator.io. For example, when exporting a record from NetSuite, the field "id" is automatically populated as the trace key. Then, Auto-resolve will apply AI/ML analysis to the trace key to attempt to resolve similar errors in identical records.

Pages (pagination)

When configuring exports with a universal connector (like the HTTP connector or the REST connector), configure the pagination strategy used by the service you are exporting data from. For dedicated connectors that Celigo has created for the service, these settings are configured automatically, but you may need to review the API documentation for services that don't use a connector that Celigo has prebuilt for the service.

Add pagination to a universal connection's export

Completed flows

You can see all your canceled and completed flows in this tab, along with all the errors that occurred during the flow run.

Completed flows

Sort your flows by flow name and by Completed date range. Your date range is customizable, from the current date to the last 30 days or however long your data retention plan allows; however, you can’t sort your date range by time.

Customize the number of Results per page ranging from 10-50 flows per page. You can also refresh the dashboard anytime to get the most up-to-date flow results.

You can run or edit a flow using the Actions overflow menu.

Errors

There are several columns you can review to better understand your errors. These columns are based on your Completed date range.

The Success and Ignored columns display the number of successful and ignored records.

The Last open error displays the timestamp for the most recent error. You can configure your account profile to display timestamps in any date/time format. If you’ve set your account to relative time, the timestamp is displayed as the length of time between the started date and time and the current date and time (1 day ago, 3 hours ago).

The Errors column displays the number of errors in your flow, not including open errors. The Auto-resolved column displays the errors that were resolved by integrator.io. The User-resolved column logs errors that were manually resolved by the user.

Runs

If you want to get a quick overview of the number of runs that's been performed for a flow, see the count in the Runs column. You can click the run count to view the Run history, which provides details of each flow run. You can also filter the run history for any analysis.
Click the arrow next to a flow to drill down and see details at a more granular flow step level. 

Pages (pagination)

When configuring exports with a universal connector (like the HTTP connector or the REST connector), configure the pagination strategy used by the service you are exporting data from. For dedicated connectors that Celigo has created for the service, these settings are configured automatically, but you may need to review the API documentation for services that don't use a connector that Celigo has prebuilt for the service.

Add pagination to a universal connection's export

When you click an error, a pop-up displays all your exports and imports, the open error count for each flow step, and the date and time of the last open error. From there you can click the flow step with errors and review both open and resolved errors.

Flow steps with errors

Open Errors

In the Open errors tab, you can review the unresolved errors that occurred for every run in the flow.

Open errors

Note: You can toggle between a new unified view (default) and the old list view; but, the option to toggle views is only available in the Open errors tab. That is, the unified error view applies to open errors.

From here you can Search for, Resolve, Retry or Refresh the error(s). Errors have a unique Message and Code that you can use to determine the type of error you’ve encountered. Download the errors to get the data as a CSV file.

The Source filter tells you where your error originated. Narrow this down to any area of your flow.

The Classification filter categorizes errors automatically according to their properties, like code, message, and source fields. For more information, see Error classifications. Classifications include:

• all classifications
• connection
• duplicate
• governance
• intermittent
• missing
• parse
• value

Filter your Timestamp to search for every instance that the error occurred in. Either today, yesterday, in the past 24 hours, 7 days, 15 days, 30 days, or define a custom timeframe.

In the default unified error view when you select an error, the row is highlighted and the Error details are displayed beside the error. 

• Edit retry data: opens the failed record in a text editor for modification.
• View HTTP request: displays the HTTP request sent from integrator.io.
• View HTTP response: displays the HTTP response returned from the application.
• Error fields: shows the error-related fields.

When you retry or resolve errors, you can view the details in the Retries tab.

Resolved Errors

The Resolved errors tab is identical to the Open errors tab, except for the Resolved by, Resolved at, and Actions columns.

Resolved errors

Resolved by identifies the account user that resolved the error. This can be an authorized user or it can be auto-resolved by integrator.io.

Resolved at displays the date and time that your error was resolved. These dates are in your account’s selected Date and Time format. If you’ve opted to show your timestamps as relative, it displays the amount of time elapsed since an event occurred, like 1 hour ago or 1 day ago.

You can take several Actions when reviewing a resolved error. These vary depending on the type of error. Some example actions are:

• Edit retry data: allows you to edit how your data is imported.
• Retry: retry your error.
• View error details: a breakdown of the error and the trace key.
• Additional actions based on the type of flow: you may see additional actions that are based on the type of connection you’re using. Here’s an example:
  • HTTP connection
    • View HTTP request: displays the HTTP request you sent to your application
    • View HTTP response: displays the HTTP response your application sent (the complete context for the Message).