These are the limits built into automations. A flow that goes past a size limit is not saved.

Flow size

Value ranges

Numbers outside a range are pulled back to the nearest allowed value when the flow is saved.

Text lengths

Behaviours to know

A flow runs once for each form submission, form sent, subscription or video. For triggers about the trainee as a whole, it runs once for each trainee and is not repeated later. See Automations overview.
Inactivity, missing workouts, expiring subscriptions, calorie and aerobic goals, pauses, stale plans, unfilled forms, waiting videos and birthdays are checked hourly. Tasks that close by themselves are also closed in that hourly check.
A push with no text, a WhatsApp step for a trainee with no phone, a webhook with no address: each is skipped and the flow continues. Nothing warns you at the time.
If a flow is interrupted and resumed, the steps that already ran are not repeated. A trainee does not get the same message twice from one run.
Its number is always read as days, even if Hours is selected.
The birthday check compares the day and month of the birth date with today’s date in universal time. Around midnight, the task can appear a few hours before or after the local start of the day.
A WhatsApp step using one of the four Perform templates sends nothing for now. Use your own SmartSend templates or a free message. See Actions.
The Unlock content step does not show your studio’s content yet and opens no content. See Actions.
Run test and the webhook step’s Send test do not send anything outside the builder.
While a Create task step is on Specific team members with nobody picked, the flow is not saved and no error appears.
Once a studio is archived, its automations stop, including flows that were in the middle of a wait.

Connected tools

See Connecting Make and other tools and Webhooks.