Resolve usage limits, rate limits, account restrictions.
Explore this topic across different AI tools to compare symptoms, common root causes, and the fastest troubleshooting paths.
ChatGPT temporarily restricts accounts after approximately 5–10 failed login attempts within a short period as a brute-force protection measure — the automatic cooldown typically lasts 15–30 minutes. Stop all login attempts immediately, wait at least 30 minutes, then try once from an incognito window on a clean network without a VPN.
If ChatGPT flags suspicious activity or temporarily restricts access, stop repeated retries first. Then sign out, use a clean browser session, disable VPN/proxy and request-modifying extensions, and retry from a stable network. If the warning appears across multiple clean environments, collect the exact message and escalate instead of forcing more attempts.
ChatGPT Plus allows approximately 160 GPT-4o messages per 3-hour rolling window before automatically downgrading you to GPT-4o mini. Free users get roughly 10–15 GPT-4o messages per 3-hour window. The cap resets on a rolling basis — not at midnight — meaning if you sent your first message at 2 PM and hit the limit, you regain access around 5 PM, not at midnight. Switch to GPT-4o mini immediately to keep working while you wait.
If you hit a daily cap, wait for reset, reduce heavy requests, and use smaller prompts. Check whether your plan has different limits.
ChatGPT is available in over 160 countries, but specific features — including Advanced Voice Mode, DALL-E image generation, and some GPT Store capabilities — roll out region by region and may not be available everywhere simultaneously. Check openai.com/policies/usage-policies for the current list of restricted countries and features before assuming the issue is account-specific.
When ChatGPT blocks you due to limits: pause retries, check your plan/usage window, reduce concurrency, and avoid automation spikes. If limits are plan-based, wait for reset or upgrade.
ChatGPT temporary restrictions typically last 1–24 hours and are triggered by behaviors that look automated: rapid retries, frequent IP changes, VPN switching, or many failed logins within a short window. Stop retrying immediately, clear your session, disable VPN, and wait at least 30 minutes before attempting a clean sign-in from a stable network.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
If ChatGPT looks blocked by regional restrictions, first confirm it’s not a browser/session/workspace issue by testing incognito + a second network (hotspot). Then disable VPN/proxy and retry. If the same restriction appears across multiple devices and networks, collect the exact message and escalate—don’t keep retrying.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
ChatGPT Plus ($20/month) in 2026 gives approximately 160 GPT-5.5 messages per 3-hour rolling window. GPT-4o was retired from ChatGPT in February 2026 and replaced by GPT-5.5 as the default model. o1 is limited to roughly 50 messages per week, o3-mini to 50 per day. When you hit the cap, ChatGPT falls back to a lighter model automatically.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the rate limit to reset (usually 1-3 hours), upgrade to ChatGPT Plus for higher limits, or reduce your message frequency.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
ChatGPT's context window limit is approximately 128,000 tokens for GPT-4o — roughly 100,000 words of combined input and output. When you hit 'request too large,' your conversation history plus your new message exceeds this limit. The fix is to start a new conversation and paste only the relevant context, rather than continuing in a thread that has grown too long.
A ChatGPT suspicious activity flag typically triggers a 24-hour cooldown period — stop all login attempts immediately, disable your VPN, and wait. The system flags activity when it detects logins from multiple geographic locations within a short timeframe, rapid failed login attempts, or access patterns that resemble automated tools. After 24 hours, log in once from your regular network without a VPN.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
ChatGPT allows up to 10 files per conversation and a maximum of 512 MB per file. If you hit the upload limit within a conversation, start a new conversation — file counts reset per conversation, not per day. Spamming retry attempts after hitting limits can trigger a temporary suspicious activity flag; wait and plan your uploads instead.
When ChatGPT blocks you due to limits: pause retries, check your plan/usage window, reduce concurrency, and avoid automation spikes. If limits are plan-based, wait for reset or upgrade.
ChatGPT Plus users get approximately 40–80 GPT-4o messages per 3-hour window before hitting rate limits; free users get a lower cap on GPT-4o mini. Usage limits reset on a rolling window, not at midnight — so if you hit a limit, you typically regain access within 1–3 hours rather than waiting until the next day.
If you hit an attachment count limit, remove older attachments, split work into multiple chats, compress files, and upgrade plan only if the limit is plan-based.
If a feature is unavailable, confirm plan/workspace, refresh billing state, and retry in a clean session. If it’s a rollout, wait and retry.
Claude's context window holds up to 200,000 tokens on paid plans — roughly 150,000 words. As conversations grow long, Claude's accuracy on earlier content degrades before the hard limit is hit. The most effective strategy is to start fresh conversations with a structured summary of essential context rather than continuing one extremely long thread. Keep project files concise and use Claude Projects to persist only what Claude genuinely needs.
Claude temporary restrictions occur when usage patterns trigger automated safety checks — sending many rapid messages, unusual request patterns, or content that approaches policy limits. Most restrictions are temporary and lift within a few hours. To avoid them: use Claude at a natural pace, start new conversations instead of sending dozens of messages in a single thread, and avoid testing content policy limits with repeated edge-case requests.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Claude Free users typically get around 10-20 messages before hitting a usage pause. Claude Pro ($20/month) gives approximately 5x more capacity. Limits are based on compute usage — not a fixed message count — so long responses drain your quota faster than short ones. When you hit the limit, Claude tells you and shows a cooldown timer. The most effective way to avoid lockouts: keep conversations shorter, start new chats instead of extending old ones, and use Claude for targeted tasks rather than open-ended exploration.
Claude Pro costs $20/month (or $18/month billed annually) and gives approximately 5x the message quota of the free tier, plus priority access during peak hours. The exact daily message count is not published by Anthropic, but Pro users consistently report 100+ messages per day under normal use before hitting any cap. Limits reset on a rolling 8-hour window, not at a fixed midnight.
Claude Free gives you limited access to Claude 3.5 Sonnet with a low message cap (roughly 10-20 messages before hitting a pause). Claude Pro ($20/month) gives you 5x more usage, priority access during peak times, access to Claude 3 Opus, Projects for persistent memory, and longer context. If you use Claude daily or for long conversations, Free runs out fast — Pro is designed for sustained use.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
If you hit rate limits, slow down requests, wait, and avoid rapid retries. If using automation, add exponential backoff and reduce concurrency.
Claude Pro enforces a 5-hour rolling usage window — not a daily reset. When you exhaust that window, you must wait until the oldest messages age out before the quota refreshes. Free users face stricter caps with no fixed window. As of May 6, 2026, Anthropic removed peak-hour throttling for Pro and Max subscribers, so you no longer get slower responses during busy periods (5am–11am PT). To continue working sooner: upgrade to Max ($100–$200/month for 5x–20x more headroom), batch your messages, or switch to shorter conversations.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
If a request is too large, shorten context, remove big uploads, and split prompts. Use multiple turns and avoid pasting huge logs in one go.
Claude throttles Pro and Max users during peak hours (5 AM to 11 AM PT / 8 AM to 2 PM ET / 13:00 to 19:00 GMT), causing the 5-hour usage window to deplete 2–3x faster than normal. Between March and May 2026, some Claude Max users reported their full session quota exhausting in under 19 minutes during peak times. On May 6, 2026, Anthropic partially removed peak-hour throttling for Pro and Max users, but heavy usage during high-demand periods can still trigger slowdowns.
If you hit too many requests, slow down, wait, and avoid rapid retries. If using automation, add backoff. Test another network to rule out VPN loops.
When Claude blocks you due to limits: pause retries, check your plan/usage window, reduce concurrency, and avoid automation spikes. If limits are plan-based, wait for reset or upgrade.
When Claude blocks you due to limits: pause retries, check your plan/usage window, reduce concurrency, and avoid automation spikes. If limits are plan-based, wait for reset or upgrade.
Claude's usage limits reset on a rolling 8-hour window, not at a fixed midnight. Free users typically get 10–20 messages before hitting the cap; Claude Pro users get approximately 5x that amount with priority access during peak hours. To continue immediately: upgrade to Claude Pro ($18/month billed annually), switch to Claude Haiku (separate, lighter cap), or start a fresh conversation to avoid heavy context overhead.
Claude Pro does not reset at a fixed daily time. Instead, it uses a rolling 5-hour window: your usage allowance refills 5 hours after your first message in a session, not at midnight. Claude Max ($100–$200/month) uses the same rolling system but with a significantly higher cap. The most efficient times to use Claude Pro are between 11 PM and 5 AM PT, when server load is lowest and your quota stretches furthest.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Midjourney enforces a concurrency limit of 3 simultaneous Fast mode jobs on Standard plans and up to 12 on Mega — when you hit the rate limit, wait 60 seconds before retrying, reduce parallel requests, and switch to Relax mode if available on your plan to continue generating without consuming GPU hours.
Midjourney's automated content moderation uses a keyword and context filter that blocks prompts containing terms related to violence, nudity, or specific real-world figures — removing or rephrasing just the flagged term usually unblocks the generation. Midjourney's filter is not perfect and sometimes flags benign words; try rephrasing with synonyms, adding descriptive art-style context, or breaking complex prompts into simpler components.
Midjourney Basic plan includes approximately 200 image generations per month (roughly 6–7 per day); Standard plan provides 15 hours of GPU time per month with unlimited relaxed generations. When you hit your daily or monthly cap, wait for the reset window or upgrade your plan to continue generating.
Midjourney limits are monthly, not daily — the Basic plan gives 200 image generations per month, Standard gives 15 fast GPU hours plus unlimited Relax mode, Pro gives 30 fast GPU hours, and Mega gives 60 fast GPU hours. If you hit the limit, you can switch to Relax mode (Standard and above), buy additional fast GPU hours (~$4/hr) in the Manage Subscription portal, or wait until your next billing cycle. Use /info in Discord to check your exact remaining balance.
Midjourney temporary restrictions are triggered by behaviors that resemble automated abuse: submitting dozens of jobs in rapid succession, repeatedly attempting blocked content, logging in from multiple unusual IP addresses, or making excessive API calls. Restrictions typically last 24 to 72 hours and lift automatically. To avoid them, pace your generations, use one stable network connection, and avoid retrying content-moderation-blocked prompts more than 2-3 times.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Midjourney's 'rate limit exceeded' error means you have sent too many simultaneous requests — Standard plans allow 3 concurrent Fast jobs, Pro and Mega allow up to 12. Stop all requests, wait 60 to 120 seconds, switch to Relax mode using the /relax command, and resume with one job at a time.
Midjourney rate limits cap you at 3 concurrent Fast mode jobs on Basic and Standard plans — when you hit the limit, stop new requests, wait 60 seconds, then use the /relax command to switch to unlimited Relax mode if you are on Standard or higher, or simply wait for your current jobs to finish before submitting new ones.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Midjourney's 'too many requests' error triggers when you exceed 3 concurrent Fast jobs on Basic and Standard plans — stop submitting new requests, wait 60 to 120 seconds, switch to Relax mode with /relax if on Standard or higher, and limit yourself to 1 to 2 jobs at a time going forward.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Midjourney's 'usage limit reached' message means your fast GPU minute allocation for the current billing cycle is exhausted. Standard and Pro subscribers can switch to Relaxed mode to keep generating at no extra cost. Basic plan users must wait for their billing cycle to reset or upgrade their plan.
Midjourney's usage limit means your monthly Fast GPU hours are exhausted — Basic plan gets approximately 200 images, Standard gets 15 Fast GPU hours, Pro gets 30 hours, and Mega gets 60 hours. To continue generating: switch to Relax mode with /relax (Standard+), purchase additional Fast hours at midjourney.com/account, or upgrade your plan.
OpenClaw flags accounts for suspicious activity when it detects patterns like API key sharing across multiple IP addresses, an unusually high number of failed authentication attempts within a short window (typically more than 10 failed logins in 5 minutes), or automated login scripts that bypass normal OAuth flows. Most temporary restrictions lift automatically within 1 to 4 hours — do not attempt repeated logins during this window, as each failed attempt resets the cooldown timer.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the targeted steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the targeted steps below.
Perplexity Pro users get 200 Pro searches per week (resetting every Monday at 00:00 UTC); API (Sonar) users have a default cap of 50 requests per minute. If you hit a rate limit, wait for the reset window or switch to Standard search mode to continue immediately.
Perplexity Pro supports file uploads up to 25 MB per file. Supported formats include PDF (text-based, not scanned), plain text (.txt), and Word documents (.doc and .docx). File upload is a Pro-only feature — free plan users do not have access. If your file exceeds the size limit or is in an unsupported format, compress it or convert it to PDF before uploading. Alternatively, paste the text content directly into the search bar, which works for most analysis tasks.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Perplexity Labs features such as Comet have a strict daily cap — typically 5 to 20 uses per day depending on the feature — separate from your standard 200 Pro searches per week. Labs limits reset at midnight UTC every day. When you hit the cap, switch to standard Pro search or Deep Research mode for the rest of the day, then return to Labs after the UTC midnight reset.
Perplexity's 'limit exceeded' message has three distinct causes: (1) Pro search weekly quota of 200 searches exhausted — wait until Monday 00:00 UTC; (2) Deep Research monthly quota of 20 sessions used up — wait until the 1st of next month; (3) Free plan daily quota of ~5 Pro searches reached — wait until 00:00 UTC tonight. Switch to Standard search to continue immediately in all three cases.
Perplexity temporary restrictions are triggered by 3 main behaviors: submitting more than 20 to 30 queries in a short period, repeatedly switching between VPN server locations during a session, or using browser automation scripts that mimic bot traffic. If you are flagged, stop all activity and wait 1 to 4 hours for the restriction to lift automatically. Do not attempt to bypass the block by creating a new account — this risks a permanent ban. For persistent restrictions, email support@perplexity.ai.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Perplexity Pro's message limit dropped from 600 to 200 Pro searches per week in May 2026, resetting every Monday at 00:00 UTC. When you hit the limit, switch to Standard (Default) search mode immediately — it is unlimited and free. To check how many searches you have left, go to perplexity.ai/settings/account.
Perplexity Pro search limits changed in late 2025 from a daily cap to a weekly cap. As of 2026, Pro subscribers get approximately 200 Pro searches per week (not per day), with file uploads capped at 50 per week. Quick searches remain unlimited. Limits reset weekly, not at midnight UTC daily. If you hit the cap, switch to Quick search or wait for the weekly reset.
As of May 2026, Perplexity Pro includes 200 Pro searches per week (down from 600) and 20 Deep Research reports per month (down from 50); limits reset every Monday at 00:00 UTC. Standard searches are unlimited on all plans. When you hit the cap, switch to Standard mode or wait for Monday's reset — there is no way to purchase additional Pro searches mid-cycle.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Perplexity Pro gives you 200 Pro searches per week; the counter resets every Monday at 00:00 UTC. If you hit the cap, switch to Standard mode immediately — Standard searches are unlimited for Pro users. For temporary 429 errors caused by sending too many requests too fast, wait 60 seconds and slow down your request pace; this is rate throttling, not a quota exhaustion.
Perplexity Free gives you unlimited Quick searches with the default Sonar model. Perplexity Pro ($20/month) adds 300 daily Pro searches using premium models like GPT-4o, Claude 3.5 Sonnet, and Gemini — plus unlimited file uploads and image generation. For casual use, Free is enough. For research, document analysis, or daily power use, Pro pays for itself quickly.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Perplexity's 'rate limit exceeded' error has three causes: (1) sending requests too fast in the API — wait 60 seconds and retry with exponential backoff; (2) exhausting your weekly 200 Pro searches — switch to Standard mode or wait until Monday 00:00 UTC; (3) exceeding the API default of 50 requests per minute — slow your request rate to 1 request per 1.2 seconds. Each scenario has a different fix.
Perplexity rate limits are triggered when you send too many searches too quickly or hit your plan's daily Pro search cap (300/day for Pro users). Wait for the throttle to clear, switch to Quick search (unlimited), or slow down your request pace.
To avoid hitting Perplexity throttle limits, default to Standard mode for routine searches and reserve Pro mode for queries that genuinely need deeper web access. Pro users get 200 Pro searches per week (resets Monday 00:00 UTC), so spreading them across 5 days gives you a safe budget of 40 Pro searches per day. Use batch-style queries — combine multiple related questions into one well-structured prompt — to get more value from each Pro use.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Perplexity Sonar API defaults to 50 requests per minute (RPM) and 1,000 requests per day on the base tier. When you exceed either limit, the API returns a 429 Too Many Requests error. Fix it by implementing exponential backoff with a minimum 1-second delay between retries, reducing request concurrency, and applying for a higher-tier limit increase through the Perplexity developer portal.
Perplexity Pro allows file uploads up to 50 MB per file, with a limit on total uploads per session or week. When your upload quota is exceeded, the fastest workarounds are: paste the text content of your document directly into the chat instead of uploading the file, split large documents into smaller chunks and upload them in separate sessions, or use URLs to share online documents rather than file uploads.
Perplexity Pro allows 200 Pro searches per week (reduced from 600 in May 2026) and 20 Deep Research reports per month; limits reset every Monday at 00:00 UTC. Free users get approximately 5 Pro searches per day. If you hit your cap, switch to Standard search mode to keep working until reset — Standard searches never count against your quota.
Perplexity has three separate usage limits depending on what you hit: Pro search quota (200 searches per week for Pro users, resets Monday 00:00 UTC), Deep Research quota (20 sessions per month for Pro users, resets on your billing date), and free tier Pro search (approximately 5 Pro searches per day, resets daily at midnight UTC). Standard searches on the free tier are unlimited. Identify which limit you hit, then follow the matching fix below.
Perplexity has two distinct restriction mechanisms that are frequently confused: usage limits (your weekly Pro quota of 200 searches is fully depleted — only resets Monday 00:00 UTC) and throttling (too many requests sent in a short burst — clears in 60 to 120 seconds without any quota impact). Distinguishing them is the first step: if Standard mode still works but Pro is blocked, it is a usage limit. If all searches fail briefly then recover, it is temporary throttling.