Upgrade to Error Management 2.0

You’ve been invited to be among the first integrator.io customers to experience Error Management 2.0 – a new paradigm for handling integration tasks more efficiently and effectively. EM2.0 is being rolled out on an opt-in basis – by signing up, you can take advantage of its powerful visual and automated tools. EM2.0 is available for integrator.io account types as follows:

• All accounts are now eligible – contact Celigo Support if you would like to request a manual Integration App upgrade to a Sandbox account (required to properly run EM2.0)
• Q2 – Q3 2021: Planned timeline for automatically upgrading all accounts to EM2.0

Get started now!
[integrator.io customers] Get started now!
[eu.integrator.io customers]

What’s been enhanced?

• Error notification in integrator.io
• Error notification from email alerts
• Flow run console
• Tools for searching and resolving errors in bulk
• New graphs to view key metrics
• Visibility to errors programmatically
• Automatically resolve duplicate errors

The new error management features are all designed to speed up your review process (compare to current features). And we promise much more to come to resolve errors faster and more intelligently!

Error notification in integrator.io

You can now see errors for enabled flows directly on the homepage integration tile and in the integration flow list – at a glance you can find out which flows have errors to review.

In Integration App tiles, you can see a summary of the errors by store and by flow category.

Error notification from email alerts

We check for new and newly resolved errors every 15 minutes, then send any necessary email notifications with a summary of new, resolved, and open errors, along with error details.

An account owner can subscribe to email error alerts within Flow Builder, as well as sign up other users to receive the notifications. (All email notifications set up in the previous error management are automatically applied to EM2.0, as well.)

Flow run console and run history

You now have a flow run console where you can watch a flow while it is running and access the errors as they’re reported (even before the flow run has completed).

The flow Run history tab displays run results for the past 30 days or the last 1,000 runs. It is important to keep in mind that the run history contains a snapshot of the flow’s results and will not be updated. For example, if you ran a flow a month ago with 100 errors and resolved 100 errors, the run history still reflects that that run produced 100 errors.

Tools for searching and resolving errors in bulk

When you are reviewing errors for a flow, you now can see all open errors for an integration step, filtered by the error source or time occurred. You can even perform a full-text search for specific error messages.

Within the error table, you can perform mass actions on the records, and you are no longer constrained by reviewing the errors per execution run. You can then retry any errors and see whether the retry has completed. When the retry is not successful and the error record has a tracekey, you’ll see a new error with a label “Retry failed” added to its error message.

The retry status is maintained only for your current session. Whenever the session times out or you sign out, the “Retry failed” labels are refreshed.

New graphs to view key metrics

View your flow’s errors, successes, ignores, and duration over time in new visual graphs, enabling you to discover actionable information in your data.

View the graphs for a single flow’s results in its dashboard console, and view the graphs for a single flow step’s results (such as import errors) in Flow Builder. 

Graphs summarize the results based on the timespan you select, from the following options:

• Results within a minute interval, when analyzing flow runs within the last 4 hours
• Results within an hourly interval, when analyzing flow runs between 4 hours and 4 days
• Results within a daily time interval, when analyzing flow runs over more than 4 days

Note: Although you can view the flow statistics for the past year, the error retry data is available only for the past 30 days.

Visibility to errors programmatically

With EM2.0, you can access your flows’ errors using the integrator.io API and then take action programmatically. Full access tokens are required for authentication. 

https://api.integrator.io/v1/flows/<_flowid>/<_exportId || _importId>/errors
GET

https://api.integrator.io/v1/flows/<_flowid>/<_importId>/resolved
PUT
Request body: { "errors": ["<_errorId1>", ... , "<_errorIdn>"]}

https://api.integrator.io/v1/flows/<_flowid>/<_importId>/retry
POST
Request body: { "retryDataKeys": ["<_retryDataKey1>", ... , "<_retryDataKeyn>"]}

You can add the following query parameters to this API to narrow down the results you want to see:

• occurredAt_lte (time value is UTC in ISO format)
• occurredAt_gte (time value is UTC in ISO format)
• Source

The API calls handle up to 1,000 errors; use pagination to fetch the next 1,000. 

For example, you could use the API within a routine or integration that displayed errors for a specific flow on Slack. Then, team members in Slack could mark these errors as resolved or retry them.

Automatically resolve duplicate errors

After you migrate your account to EM2.0, Auto-resolve will be enabled on the account so that you can leverage auto-resolve to mark duplicate errors resolved in the following scenarios:

• Auto-resolve will automatically mark all previous error records with the same trace key as the latest error record as resolved, leaving only the most recent errors open.
• If a record is successfully processed, then all errors that have the same trace key as the successful record’s are automatically marked as resolved – assuming that you fixed the flow configuration and reran it.

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.

A more powerful way
to manage integration errors

Get started now!

Current error management vs. EM2.0

The following table gives you an at-a-glance comparison of concepts and features that will be deprecated in EM2.0 and how you will gather the information and resolve errors differently going forward:

Comments

Leave a comment below, and we’ll respond to your questions or suggestions.