Set alerts for long-running flows

Long-running flow alerts let you proactively monitor flows that run longer than a limit you set. These alerts inform you about unexpected delays as soon as they happen — even when you're away from integrator.io — instead of hearing about them from a downstream partner or catching them during a manual dashboard check. They're available on every integrator.io plan at no additional cost, for both integration app and custom flows. Setting one up doesn't affect the flow itself — it only monitors the flow's run time and notifies the recipients you choose.

Prerequisites

• Permissions – You need Account Owner, Admin, Manage all, Custom Manage, Monitor all, or Custom Monitor access to the integration. A Monitor-level user can create an alert but can only add themselves as a recipient; see Manage long-running flow alerts for the full permissions table.
• A flow to alert on – The flow doesn't need any prior run history to create an alert, but limit guidance (a suggested value and a historical runtime chart) only appears once the flow has completed runs to draw from.

A single flow alert 

You can receive long-runtime alert emails when a specific flow runs longer than the limit you set. To set one limit for all flows in an integration at once instead, see All flows (integration) alert.

Create the alert

1. Open the integration that contains the flow.
2. Select the Alerts tab. 
   The Alerts tab was previously named Notifications. Your existing Notify me of flow errors and Notify me when a connection goes offline settings are unchanged and still appear at the top of this tab.
3. In the Long run time alerts section, select Create.
4. In the Flow field, select the flow you want to alert on.
5. Under Get an alert when this flow runs longer than, enter a limit in Hours and Minutes.
   As you enter a value, integrator.io shows how many of the flow's past runs would have triggered an alert at that limit — for example, "6 of 90 runs in the last 30 days would have triggered." Use this to check whether your limit is too tight (too many past runs would have triggered it) or too loose (it wouldn't have caught a run you consider a problem) before you save. The minimum value is 5 minutes.
6. Optional: Select a different look-back period, and review the suggested limit and historical runtime chart to help you choose a value instead of entering one from scratch. See Historical runtime chart and limit guidance for how to read this section.
   If the flow is new or hasn't run enough times in the selected period, no suggestion appears. Enter a limit manually — you can revisit it later once the flow has more run history.
7. Under Recipients, add at least one person to notify when the alert triggers. A recipient must be added before you can save the alert.
8. Select Save alert.

A long-runtime alert doesn't cancel, pause, or otherwise change how the flow runs. To stop a run that has triggered an alert, use the Cancel run action from the Running flows dashboard or Run console.

How integrator.io monitors a flow run by set limit

Once saved, integrator.io monitors the flow's in-progress runs against your limit. If a run exceeds the limit, an alert indicator appears on the Running flows dashboard, in Run history, and in the Run console, and each recipient receives an email. 

For a multi-instance flow, integrator.io monitors and alerts on each instance separately, using the same limit. For a multi-source flow, one limit applies across all sources. see Multi-source and multi-instance flows.

All flows (integration) alert

An integration-wide long-runtime alert default applies one runtime limit to all flows in an integration, including flows you add later, so you don't have to configure an alert on each flow individually. To alert on a single flow instead, see Set up a long-runtime alert on a flow.

Use an integration-wide default when you manage many flows and want a baseline safety net, then set a tighter or looser limit on individual flows that need one.

Set an integration-wide default

1. Open the integration.
2. Select the Alerts tab.
3. In the Long run time alerts section, select Create.
4. In the Flow field, select All flows.
5. Under Get an alert when this flow runs longer than, enter a limit in Hours and Minutes.
   The suggested limit, typical runtime range, and historical runtime chart aren't available at this scope, because a single limit is being applied across flows with different normal run times. Enter a value based on your own knowledge of the integration. A low limit can trigger alerts for flows that are running normally, so start with a conservative value and narrow it later using per-flow overrides.
6. Under Recipients, add at least one person to notify when the alert triggers.

7. Select Save alert.

Once saved, every flow in the integration — including flows added afterward — is monitored against this limit, except for flows that have their own alert (see below).

How per-flow overrides work

A limit set directly on a flow always takes precedence over the integration-wide default for that flow. A flow can't carry both a default-inherited limit and its own limit at the same time — setting one on the flow replaces the default for that flow only; every other flow in the integration keeps using the default.

To override the default for one flow, follow the steps in Set up a long-runtime alert on a flow and select that specific flow instead of All flows.

Multi-source and multi-instance flows

• Multi-source flows – integrator.io monitors each source run individually, but a multi-source flow uses a single limit across all of its sources; you can't set a different limit per source. The historical runtime chart isn't shown for multi-source flows, because runtimes across sources can vary too widely to chart meaningfully.
• Multi-instance flows – Each instance generated from the multi-instance flow is monitored and alerted on separately, using the same limit.

Historical runtime chart and limit guidance

When you create a long-runtime alert on a single flow, integrator.io shows a suggested limit, a typical runtime range, an estimated trigger frequency, and an expandable historical runtime chart, so you can pick a limit based on the flow's own run history instead of guessing. This reference explains what each of these values means and when they're available.

Limit guidance

This guidance appears only when you're creating or editing an alert on a single flow. It isn't available for an integration-wide default or for a multi-source flow — see All flows (integration) alert for why.

Reference

No guidance

If a flow is new, or hasn't run enough times in the selected look-back period, integrator.io doesn't show a suggested limit, typical range, or chart. Enter a limit manually. Once the flow has more run history, either edit the alert to see updated guidance, or select a longer look-back period.

Related articles

• Manage long-running flow alerts
• Get error alerts or notifications via email (You only)
• Configure error alert or notification email for other users