Monthly flow runs
How flow runs are counted, what stops when a server runs out for the month, which modules keep working, and the per-minute limits that stop loops.
Every time a flow runs, it counts toward the server’s runs for the month. Free and Plus have a monthly cap; Pro has none. The counts are in Plans and limits. The count starts again on the 1st of every month, UTC.
What counts as a run
A run is one flow starting once: your own flows, and the flows Gildi’s modules make for you. That means module work counts too:
- Welcome & Goodbye: each welcome, goodbye and auto-role
- Moderation: each command, and each time a filter catches a message
- Anti-raid
- Timed messages
- Levels and Economy: their commands and level-up messages
Some modules aren’t made of flows at all, so they never use runs: Tickets, Role menus, Giveaways, Forms, Verification, Starboard, Suggestions, Birthdays, Stats channels, Sticky messages, Temporary voice, Invite tracking and Appeals.
When a server goes past its cap
There’s a soft margin, so one busy month doesn’t cut you off:
- Past the cap, the dashboard warns you, and flows keep running.
- At one and a half times the cap, flows stop until the 1st of next month. That includes the flows modules make: welcomes, moderation commands and filters, anti-raid, timed messages, and level and economy commands.
Audit logs are the exception: they’re never stopped by a plan. Modules that aren’t flows, like Tickets and Role menus, keep working too.
When a stopped flow was a command or a button, the member sees: “This server has used its flow runs for this month. An admin can see more on the Gildi dashboard.” Other flows stop without a message.
Upgrading raises the cap straight away.
Per-minute limits
A separate limit stops your own flows from running away, usually when two flows keep starting each other. It applies to custom flows only, not to the ones modules make:
| Started by | Limit per flow |
|---|---|
| A member, like a command or a message | 90 runs a minute for each member |
| No member, like a server-wide event | 600 runs a minute |
Past it, the flow skips runs until the next minute. A member who used a command sees “This flow is running too often. Try again in a minute.” The flow’s run history shows one line saying it was skipped. Skipped runs don’t count toward the month.
If you see this, check whether one flow’s action fires another flow’s trigger, and back again. Gildi’s other speed limits are in Rate limits.
Questions
What happens when a free server runs out of flow runs?
Gildi warns you on the dashboard and keeps running flows for a margin past the cap. Past that margin, flows stop until the 1st of next month, including the ones modules make. Logs and modules that aren’t flows keep working.
When do flow runs reset?
On the 1st of every month, UTC.
Do welcome messages and moderation commands count as runs?
Yes. Every module that works through flows counts, and stops with the rest once the server is past its margin.