A flow run in Fastgen refers to an execution of an API endpoint or workflow you have created within the platform.

The number of flow runs used when executing an API or workflow depends on how many action blocks are executed. Let's have a look at a few examples as APIs and workflows are calculated slightly different:
‍
If you make a request to an API endpoint, and 10 (or fewer) action blocks are executed in that specific request, it will count as one flow run. If you make a request to an API endpoint and more than 10 (but fewer than 20) action blocks are executed, it will count as two flow runs. Accordingly, 30 action blocks executed will count as three flow runs etc.

Important: if you have an API consisting of 50 action blocks, but only 6 of them are executed in a specific request, it will only count as one flow run.

Workflow flow runs are calculated with the same technique, just with the difference that 5 action blocks executed count as one flow run, 10 action blocks executed count as two flow runs etc..

Requests sent through the Debug Mode will not count towards your flow run limit.

An action in Fastgen refers to a single execution block within an API route or workflow. Each time a flow is run, every action block that is executed counts as one, except for Flow-Control and Response Blocks, which are free.

If you reach your flow run limit for the month, you have two options:
1. Enable 'auto-increase' to automatically purchase additional flow run 'buckets' as you need them. These are billed separately at a fixed rate.
2. Set a spending limit for your usage-based billing to avoid incurring additional charges. If you reach this limit, 'auto-increase' will be blocked.

Unused flow runs do not roll over to the next billing cycle. Each month, your flow run limit resets based on the plan you are subscribed to.