Tags are customizable labels in integrator.io that you can apply to flow errors to categorize, prioritize, and track resolution progress. Use tags to provide context—such as status levels or priority rankings—to help your team collaborate more effectively during troubleshooting. Managing flow errors effectively requires a coordinated approach between monitoring, organization, and delegation. After you investigate and resolve flow errors to identify the root cause, use tagging to route specific issues to the right team members. By combining tagging with the ability to assign errors to users, you create a searchable, prioritized backlog that ensures critical blockers are addressed first. To get started, ensure your team has the correct setup by following the guide to manage integration users and permissions, which defines who can view, apply, and manage these labels.
This article focuses on point 3 in the error management workflow below.
The following diagram represents the logical path from error detection to resolution. Use this flow to ensure errors are handled by the correct team members in a timely manner.
| Stage | What to do | Where to do |
|---|---|---|
| Monitor | Check for errors after flow runs | Dashboard / Flow builder |
| Notify | Get notified of errors only when you or your admin have subscribed to the notification mails. (However, get automatically notified when errors are assigned. | Integration page/Flow settings |
| Organize | Label errors using tags, for example, apply priority or contextual tags. | Errors page |
| Delegate | Assign errors to yourself/team for ownership, follow up, and resolution. | Errors page |
| Investigate | Review Error list/details (and other locations listed here) to identify the root cause of errors. | Errors page / Flow builder / Advanced flow editors |
| Resolve | Correct and retry any assigned errors for resolution/closure. | Errors page |
The example workflow merely indicates how errors could move from occurrence to resolution, but you can order the steps based on your scenario.
Before you start tagging errors, verify the following requirements:
- Subscription plan: Standard, Professional, or Enterprise edition.
-
Permissions: Any user with
Admin,Manage,Monitor, orCustomaccess can create, rename, delete, apply, or remove tags. - Access: Tags are available for both Open errors and Resolved errors. For open errors, you must use the unified error view.
The platform uses the following rules to maintain consistency across your account:
| Rule | Specification |
|---|---|
| Account limit | Maximum of 1,000 unique tags per account. |
| Error limit | Maximum of three tags per single error. |
| Character limit | Maximum of 100 characters per tag. |
| Case sensitivity | Tag names are case-insensitive (e.g., "URGENT" and "urgent" are duplicates). |
| Global vs. Local | Creating/editing/deleting a tag affects the entire account. Applying/removing a tag affects only that error. |
You can create tags as you encounter errors (ad hoc) or build a predefined list (planned) for your team to follow.
To update several errors at once, use the batch tagging feature:
- In the error list, select the checkbox for each error you want to modify.
- Select the Tag icon at the top of the list.
- To apply tags, select the checkboxes and specify any new/existing labels – these labels you provide will override the existing labels/tags.
- Select Apply.
In bulk tagging, it uniformly applies the tags
The platform automatically applies tags to recurring errors based on specific identifiers to save manual effort.
Errors with a retry data key
| Scenario | Result |
|---|---|
| Apply tag to open error | The tag is automatically applied to other open errors with the same retry data key. It is not applied to prior resolved errors. |
| Retry a tagged error | If the retry fails, the same tag is automatically applied to the new open error. |
| Resolve a tagged error | The resolved error record retains all applied tags for historical tracking. |
Errors with a trace key (no retry data key)
Tags are account-wide, and any changes update every error using that tag (label) across all integrations.
- Rename a tag: Select the Tag icon, select the tag name, enter the new name, and save.
- Delete a tag: Select the delete (trash) icon next to the tag and confirm Delete.
This action renames or deletes the tag for all associated errors in the account.
Filters use "OR" logic. If you select multiple tags, the results show errors that contain at least one of those tags.
- Select the Filter icon at the top of the error list.
- Select the checkbox for the tags you want to see (for example,
P1: Urgent). - Select Apply.
To reset the view, select the Filter icon and select Clear filter.