Why Wavo shows 'too many requests' or 'temporarily limited': rate limits by plan and an abuse guard against injection. How long it lasts and how to fix it.

Wavo says my account is temporarily limited

If Wavo returns "too many requests" or "your account is temporarily limited / blocked for suspicious use", you've hit one of two safeguards: a rate limit (a cap on how many messages per burst/minute/hour, briefly pausing you) or the abuse guard, which throttles or blocks accounts that repeatedly send prompt-injection / security-flagged messages. Both are temporary and self-clearing — rate limits reset in seconds, abuse throttles/blocks expire within an hour. Your credits are never lost.

Who is this for

Anyone who sees a rate-limit or "temporarily limited" message while chatting with Wavo and wants to know why it happened, how long it lasts and what to do.

Before you start

• These limits are not a billing quota. Wavo usage is metered in credits (ai-109 credits and limits); these safeguards only stop runaway loops and abuse (apps/backend/src/lib/chat-rate-limit.ts:14).
• The message you see is temporary. Note the retry-after seconds in the message and simply wait.

The two safeguards

1. Rate limits (a short pause) — code 429

To stop accidental loops or scripted flooding, Wavo caps how fast you can send messages. When you exceed a cap you get an HTTP 429 with a X-RateLimit-Reset time, and you can send again once it passes. The per-plan caps are (chat-rate-limit.ts:22):

There's also an overall safety cap of 240 messages per minute regardless of plan, and voice transcription has its own hourly limit (10/hour, 30/hour on Pro). The message names which window you hit ("burst", "per minute" or "per hour") and how many seconds to wait. Nothing is charged for a blocked request.

2. The abuse guard (temporary limit or block)

Separately, Wavo scans each message for prompt-injection and security patterns — attempts to extract its system prompt, jailbreak it, or otherwise manipulate the assistant. Normal advertising questions are never flagged. Repeated flagged messages in a rolling 1-hour window escalate (apps/backend/src/services/chat/chat-abuse-monitor.service.ts:14):

• Soft limit after 20 flagged messages → you're throttled to 1 message per minute for 1 hour. The message reads "your account is temporarily limited for suspicious use" (code CHAT_SOFT_BAN_THROTTLE).
• Hard block after 100 flagged messages → chat is blocked for 1 hour with "your account is temporarily blocked for suspicious use — contact support" (code CHAT_ABUSE_HARD_BAN, HTTP 403).

Both states are stored with a 1-hour timer and clear themselves automatically — you don't need to do anything but wait (and stop sending flagged content).

How long does it last?

• Rate limit (429): seconds to at most an hour, shown as the reset/retry time in the message.
• Soft limit: throttled to 1 msg/min, clears within 1 hour.
• Hard block: no chat for up to 1 hour, then automatically restored.

How to fix it

1. Read the wait time in the message and pause — most rate limits clear in seconds.
2. Slow down: avoid rapid repeated sends, duplicate submissions or scripted requests.
3. If you were testing prompts that look like injection/jailbreak attempts, stop — those are what trip the abuse guard. Rephrase your real question normally.
4. Wait out the hour for a soft/hard state; it expires on its own.
5. If you're hard-blocked and believe it's a mistake, contact support — hard blocks ask you to reach out.

Common issues

• "Too many requests" while working normally fast: you hit the burst or per-minute cap. Wait the few seconds shown; consider Pro for higher limits (ai-109).
• "Temporarily limited for suspicious use" but I wasn't attacking anything: something in your messages matched a security pattern. Rephrase in plain language; the throttle clears within the hour.
• Chat fully blocked with a "contact support" note: that's the 1-hour hard block from repeated flags. Wait it out or contact support if you think it's wrong.
• Voice transcription blocked: voice has a tighter hourly cap (10/hour, 30 on Pro) because it's more expensive per call.

Best practices

Don't hammer send

Rapid duplicate sends are the most common way to trip a rate limit. Send once and let Wavo answer.

Keep prompts genuine

The abuse guard only reacts to injection/security patterns. Asking real questions about your ads never triggers it — only prompts crafted to manipulate the assistant do.

Upgrade if you consistently hit caps

If normal work regularly hits the per-minute or hourly limit, Pro roughly triples the budgets. See credits and limits.

FAQ

Why does Wavo say "too many requests"?

You sent messages faster than the allowed rate — a burst, per-minute or hourly cap. It's a short, automatic pause (HTTP 429) to prevent loops and flooding, not a billing block. Wait the number of seconds shown in the message and try again; the blocked request isn't charged.

Why is my account "temporarily limited for suspicious use"?

Wavo's abuse guard flagged repeated messages that matched prompt-injection or security patterns. After 20 flagged messages in an hour it throttles you to 1 message per minute; after 100 it blocks chat for an hour. Normal advertising questions don't trigger it — only manipulation attempts do.

How long until I can use Wavo again?

Rate limits clear in seconds to minutes (the reset time is in the message). The soft "temporarily limited" throttle and the hard block both expire automatically within 1 hour — no action needed beyond waiting and not resending flagged content.

Do I lose credits when I'm rate-limited or blocked?

No. Blocked requests never reach the model, so no credits are consumed. These safeguards are separate from your credit balance and plan quota.

Can I raise my limits?

Pro plans have higher chat budgets (burst 30, 100/minute, 1000/hour vs 10/30/200 on Free) and higher voice limits. Upgrading raises the rate caps, but the abuse guard applies to every plan equally.

FAQ

Why does Wavo say "too many requests"?

You sent messages faster than the allowed rate — a burst, per-minute or hourly cap. It's a short, automatic pause (HTTP 429) to prevent loops and flooding, not a billing block. Wait the number of seconds shown in the message and try again; the blocked request isn't charged.

Why is my account "temporarily limited for suspicious use"?

Wavo's abuse guard flagged repeated messages that matched prompt-injection or security patterns. After 20 flagged messages in an hour it throttles you to 1 message per minute; after 100 it blocks chat for an hour. Normal advertising questions don't trigger it — only manipulation attempts do.

How long until I can use Wavo again?

Rate limits clear in seconds to minutes (the reset time is in the message). The soft "temporarily limited" throttle and the hard block both expire automatically within 1 hour — no action needed beyond waiting and not resending flagged content.

Do I lose credits when I'm rate-limited or blocked?

No. Blocked requests never reach the model, so no credits are consumed. These safeguards are separate from your credit balance and plan quota.

Can I raise my limits?

Pro plans have higher chat budgets (burst 30, 100/minute, 1000/hour vs 10/30/200 on Free) and higher voice limits. Upgrading raises the rate caps, but the abuse guard applies to every plan equally.

Last updated: 2026-07-02

Related articles

• Wavo credits and limits
• Wavo troubleshooting
• Wavo privacy and data usage
• Contacting Wevion support
• Wavo — your AI assistant in Wevion — complete guide