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:
- November 2020: All accounts with custom flows can choose to upgrade to EM2.0
- February 2021: All accounts with Integration Apps can choose to upgrade to EM2.0
- Q2 2021: All accounts will be automatically upgraded to EM2.0
- Only the account owner can upgrade to the new error management experience. Afterward, all other shared account profiles (Manager or Monitor role) will be able to use EM2.0.
- All integrations in the account will be migrated to the new error management.
- This is a one-time migration. You won’t be able to switch back to the current error management version.
- Autopilot is disabled by default. Contact your customer service manager to inquire about account setup.
- Salesforce – NetSuite v2 Integration App customers must migrate to Salesforce – NetSuite IO to make full use of EM2.0 features. (Also see the course Salesforce – NetSuite v2 to IO Migration: Details & Insights at Celigo University.)
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 (Autopilot add-on license)
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.
Flow run console
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).
You can also view the result of the last run.
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. You can even perform a full-text search for specific error messages or data values.
Within the console, you can perform mass actions on the records, and you are no longer constrained by reviewing the errors per execution run.
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.
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>"]}
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
The optional EM2.0 add-on, Autopilot, will automatically mark all previous error records that have the same “trace key” as the latest error record as resolved, leaving only the most recent errors open.
If there is a successful import run, then all errors that have the same trace key as the successful record’s would be automatically marked as resolved – assuming that you fixed the flow configuration and re-ran it.
A more powerful way
to manage integration errors
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.
| Error Management 1.0 | Error Management 2.0 |
|
|
|
|
|
|
|
|
Comments
Leave a comment below, and we’ll respond to your questions or suggestions.
Comments
1 comment
We are rolling this new error management framework in phases. So, please leave a comment here if you are interested in migrating to the new error management sooner rather than later.
As a reminder, if your account has Integration App (IA) or IA license or you plan to use IA, you'll need to wait till Feb 2021 to uptake the new features.
Thanks
Please sign in to leave a comment.