Cooldown

Cooldown prevents users from repeatedly triggering the verification flow in a short time span.

Why it matters

Without a cooldown, users can retry too quickly after failure or repeatedly trigger your verification logic in ways that create noise.

What cooldown protects against

• Rapid re-attempt spam
• Repeated role churn
• Extra noise in verification logs

When to enable it

Enable cooldown when:

• Verification abuse is common
• You want a more stable review window after a failed attempt
• You also use maximum verifications per user

Practical guidance

• Keep the cooldown long enough to discourage spam.
• Keep it short enough that legitimate users are not locked out for too long after a mistake.
• Document the policy in your rules if it affects normal onboarding.