Flow reference: Logic
Cooldown
Rate limit this flow per user.
Rate limit this flow per user.
When and how to use it
Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.
Configuration fields
Cooldown (seconds) — seconds
Duration in seconds. Use a numeric value, not text such as 5 minutes. Choose a small value when testing.
Input: Number.
Default:
30.Scope — scope
Select where the command or limiter applies. The same label can mean a command context or a cooldown scope; use the choices offered by this block.
Input: Fixed choice.
Default:
user.Available choices (preserve the exact value):
user — Per userchannel — Per channelserver — Per serverOutputs and next steps
out: Continue to the next step.blocked: The cooldown or guard blocked execution.Test and troubleshoot
Invoke the correct trigger with simple inputs and verify the expected effect. Confirm variables exist on this path. A preview alone does not verify Discord delivery.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).