Project execution settings

Use Advanced options in your project settings to configure automatic retries and, in an environment, single-thread mode. This page also displays the Designer's repeated-App execution limit and the server's upload size limit.

Open Advanced options

1. Open the project you want to configure.
2. Select Settings under Manage.
3. Select Advanced options from the settings menu.

Project Admins and Full Admins can save project settings. If your account cannot update projects, Save is disabled and its tooltip displays You don't have the rights for this action. See Roles and restrictions for access details.

Configure automatic retries

Under Flow options, configure the following fields:

Field	Purpose	Default allowed range
Number of Flow Retries	The number of automatic retries after an error at a flow step.	0–5 retries.
Minutes to wait on Flow error	The delay before the next automatic retry.	3–60 minutes.

The allowed ranges can differ by installation. Enter whole numbers within the ranges configured for your installation. If you save a number outside a configured range, Flowize adjusts it to the nearest allowed value.

1. Enter Number of Flow Retries. With the default allowed range, enter 0 to disable project-level automatic retries.
2. Enter Minutes to wait on Flow error.
3. Select Save in the upper-right corner.

Both fields are required. Leaving either field empty prevents saving, including when the retry count is 0.

What happens after an error

When these project settings apply, Flowize schedules the record for another attempt after the configured delay. Execution resumes at the failed step.

For example, a retry count of 2 and a delay of 5 minutes allows two additional attempts at a failed step, with a five-minute wait before each attempt.

If the retry count is exhausted, Flowize applies the flow's error-handler behavior where applicable. If execution cannot transfer to an error-handler flow, the record finishes with errors. Inspect the record and its execution steps in Reports.

How App-specific error handling interacts with retries

An App's Error handling configuration takes precedence when a rule handles the error. That rule uses its own retry count, interval, and Continue or Stop action. If the App configuration does not handle the error, Flowize falls back to the project retry settings.

Setting project retries to 0 does not disable retries configured in an App's error-handling rule. For instructions, see Error Handler for every app in the flow.

Review the repeated-App execution limit

In the Designer, Flow options displays Maximum times an App can be executed. This field is read-only. It shows the limit used to guard against repeated execution of the same App within one data record's flow execution, outside a Loop.

If this guard stops an execution, the record finishes with errors and its report identifies the App and the exceeded limit. Review the flow's connections in Flows and inspect the execution in Reports.

The field is not displayed in environment project settings.

Run records one at a time

In an environment, Flow options includes Single thread mode?. Enable it when your project needs to process data records one at a time, one after another.

1. Open the project in the environment where you want to configure execution.
2. Go to Settings > Advanced options.
3. Under Flow options, set Single thread mode? to Yes.
4. Select Save.

To turn off this mode, set the switch to No and select Save again. This option is not available in the Designer.

Single-thread mode controls project execution concurrency. To pause or resume background workers for an environment, see Worker controls and environment logs.

Review batch upload limits

Under Batch options, Upload size limit displays the server's maximum request size. The field is read-only, so you cannot change it in project settings.

A batch's permitted file size can also be lower than this displayed value. Flowize checks the project's batch file limit separately. If a request or batch file exceeds its applicable limit, the error message includes the submitted size and the permitted size.

For batch creation, payload validation, and processing steps, see Batches.