Clicking quickly through the app can produce:
You're moving faster than expected. Limits reset automatically - try again shortly.
This is a velocity guard on interactive surfaces. It resets on its own, usually within a minute, and it is not a warning about your account, not a strike, and not something to appeal.
Why it triggers on normal use
- Browser autofill or a stuck key firing the same action repeatedly.
- Multiple tabs on the same account all polling at once.
- Scripted clicking through the UI. If a script is driving the browser, use the API instead: it is faster, supported, and has published limits.
- Genuinely fast work on a very large segment, which is the least common case.
What to do
- Wait a moment and continue. Nothing was lost.
- Close duplicate tabs on the same account.
- For bulk work, switch to an export rather than many individual actions, or to the API or CLI.
Limits scale with plan, so heavier tiers have more headroom. But the design intent is that no interactive user should hit this doing real work: if you do, the workflow probably wants an export or an API call rather than more clicking.
Different message, different cause: 'Too many reveals in a short window' is a specific reveal cap, and a 429 from the API is the machine-side equivalent.