A flow's settings control how the flow as a whole behaves: its name and description, whether you're emailed about its errors, whether matching errors resolve themselves, whether its sources run at the same time or one after another, which flow runs after it, the aliases its scripts use, and any custom settings of your own. They're separate from the options on each step and from the schedule. This article describes each setting and when to change it.
- Go to Build
> Flows, and then open the flow.
- At the top right of Flow builder, select Settings.
- Change the settings described below, and then select Save.
General
| Setting | What it does |
|---|---|
| Name | The flow's name, shown everywhere the flow is listed. |
| Description | What the flow does, for anyone who opens it later. |
| Notify me of flow errors | Yes emails you when the flow has new errors. To notify other users, or to be notified about offline connections, use the integration's Alerts tab; see Set up email notifications for flow errors or offline connections. |
| Auto-resolve errors with matching trace key | Yes (the default) resolves an open error automatically when a later run processes a record with the same trace key successfully. See Resolve errors automatically or manually. |
| Export execution mode | Applies when the flow has more than one source. Parallel runs the sources at the same time; Serial runs them one after another, each source's records passing through every later step before the next source starts. New flows run in parallel; flows created before this setting existed run serially unless you change it. The setting applies to scheduled runs and to on-demand runs of more than one source; running a single source on demand ignores it. |
| Next integration flow | Runs another flow in the same integration as soon as this one completes — a customer sync followed by an order sync, say. Only flows that are turned on are listed. A scheduled run always runs the next flow; when you run the flow on demand, you can clear Run next flow(s) after current flow completes to run this flow alone. See Run a flow. |
Advanced settings
Aliases > Manage opens the aliases the flow's scripts can use to refer to its connections, exports, imports, and other resources by name instead of by ID. See Create and manage aliases to reference resources in scripts.
Custom
Settings holds any JSON settings of your own that the flow's scripts and handlebars expressions can read. Launch form builder opens the form builder, where you can give those settings a form instead of editing raw JSON. See Create forms.