When Claude displays the message “This isn’t working right now”, it usually means the service cannot complete a request at that moment. The issue may come from Anthropic’s servers, a temporary network problem, a browser conflict, an overloaded conversation, or account-related limitations. Although the error can feel vague, it is often fixable with a structured troubleshooting process.
TLDR: The Claude “This isn’t working right now” error is commonly caused by server outages, browser issues, unstable internet, overloaded chats, or temporary account restrictions. Users should first check Claude’s service status, refresh the page, and try a new chat. If the issue continues, clearing browser data, disabling extensions, switching networks, or contacting support may resolve it. In many cases, waiting a short time is enough because the problem is temporary.
What the Claude “This Isn’t Working Right Now” Error Means
The message “This isn’t working right now” is a general error that appears when Claude cannot process or return a response. Unlike a specific login error or payment warning, this message does not always explain the exact cause. It can appear while sending a prompt, uploading a file, opening a previous conversation, or waiting for Claude to generate an answer.
In most situations, the error means that something interrupted the normal request-and-response process. Claude may have received the user’s message but failed to complete it. Alternatively, the browser may have failed to communicate properly with Claude’s servers. Because the message is broad, the best approach is to test the most likely causes one by one.
Common Causes of the Error
Several issues can trigger this error. Some are outside the user’s control, while others can be fixed locally.
- Claude server problems: Anthropic’s systems may be temporarily overloaded or under maintenance.
- Internet instability: A weak Wi-Fi signal, congested network, or VPN interruption can break the connection.
- Browser cache problems: Old cookies or cached files may interfere with the Claude web app.
- Browser extensions: Privacy tools, ad blockers, script blockers, or password managers may block required scripts.
- Large or complex chats: Very long conversations, large files, or heavy prompts can sometimes cause failures.
- Account or usage limits: Users may encounter temporary restrictions if usage limits are reached.
- Device issues: Low memory, outdated browsers, or conflicting software can disrupt performance.
Step 1: Check Whether Claude Is Down
The first step is to determine whether the problem is affecting many users. If Claude’s servers are experiencing an outage, local fixes will not solve the issue. In that case, users can only wait until service is restored.
A user can check the official Anthropic status page, look for recent outage reports, or search social platforms for mentions of Claude problems. If many people are reporting the same message, the error is probably not caused by the user’s device or browser.
If there is an active outage, the most practical fix is patience. The user should wait several minutes, refresh the page, and try again later. During major service disruptions, repeated retries may not help and can make the experience more frustrating.
Step 2: Refresh the Page and Retry the Request
A simple refresh can often clear a temporary loading failure. The Claude web app may have lost connection while processing the prompt, or the browser may have failed to load a required resource.
The user should refresh the tab, wait for Claude to fully reload, and then try sending the prompt again. If the same conversation keeps failing, starting a new chat is often more effective. A previous thread may contain too much context, a corrupted state, or an uploaded file that is causing the problem.
When retrying, the user should avoid sending the exact same large request repeatedly. Instead, they can simplify the prompt, remove unnecessary details, or ask Claude to complete the task in smaller parts.
Step 3: Start a New Conversation
Long Claude conversations can become more difficult to process over time. If a chat contains many messages, long documents, pasted code, or complicated instructions, Claude may struggle to continue the thread. Starting a new conversation gives the system a cleaner context.
To preserve important information, the user can copy a short summary from the old conversation and paste it into the new one. The summary should include only the essential background, goals, and constraints. This reduces the processing load and may prevent the error from returning.
Example: Instead of copying an entire 20-page discussion, a user might write: “The task is to rewrite a product description in a professional tone, keep it under 150 words, and include three benefits.” A shorter prompt is easier for Claude to process and less likely to fail.
Step 4: Clear Browser Cache and Cookies
Browser cache and cookies help websites load faster, but they can also cause problems when stored data becomes outdated or corrupted. If Claude recently updated its web app, older cached files may conflict with the current version.
Clearing cache and cookies can fix login loops, broken buttons, loading errors, and response failures. The user should clear site data for Claude or clear the browser’s recent cache and cookies. After that, they should close the browser, reopen it, sign in again, and test Claude with a short prompt.
This step is especially useful if Claude works on another device but not on the original browser. That pattern often points to a local browser issue rather than a Claude-wide problem.
Step 5: Disable Browser Extensions
Browser extensions can interfere with web apps. Extensions that block scripts, trackers, pop-ups, cookies, or third-party requests may accidentally block parts of Claude’s interface. Even helpful tools can create conflicts after a browser or website update.
The user can test this by opening Claude in an incognito or private browsing window with extensions disabled. If Claude works normally there, an extension is likely responsible. The user can then disable extensions one at a time to identify the source of the conflict.
Common extension types that may cause issues include:
- Ad blockers
- Script blockers
- Privacy and anti-tracking tools
- VPN browser extensions
- Grammar or writing assistants
- Custom CSS or interface modification tools
Step 6: Try a Different Browser or Device
If disabling extensions does not help, switching browsers is a useful test. A user who normally uses Chrome can try Firefox, Edge, Safari, or another modern browser. If Claude works in a different browser, the problem is likely related to browser settings, extensions, cache, or version compatibility.
Testing on another device can also reveal the cause. If Claude works on a phone but not a laptop, the issue may be device-specific. If it fails everywhere on the same account, the issue may be related to the account, service status, or network.
The browser should also be updated. Outdated browsers may not support the latest web technologies used by modern AI applications. Keeping the browser current improves security and reduces compatibility problems.
Step 7: Check the Internet Connection
Claude depends on a stable connection. A connection can appear to work for basic browsing while still failing during longer AI responses or file uploads. If the network drops briefly, Claude may show “This isn’t working right now” instead of completing the answer.
The user can try the following network checks:
- Restart the router or modem.
- Move closer to the Wi-Fi router.
- Switch from Wi-Fi to mobile data, or from mobile data to Wi-Fi.
- Disable a VPN or proxy temporarily.
- Pause large downloads, streaming, or cloud backups.
- Run a speed test and check for packet loss or unstable latency.
Corporate, school, or public networks may also block certain traffic required by AI tools. If Claude works on a home network but not at work or school, network filtering may be involved.
Step 8: Reduce Prompt Size and File Complexity
Large prompts and complex files increase the chance of failure. Claude can handle substantial context, but there are still practical limits. A massive document, a long spreadsheet, or a prompt with many competing instructions may cause processing problems.
Users should break large tasks into smaller steps. For example, rather than asking Claude to analyze an entire report and produce a full strategy in one message, the user can ask it to summarize one section first, then extract key points, then draft recommendations.
When uploading files, the user should check whether the file is unusually large, corrupted, password-protected, or in an unsupported format. Converting a file to a cleaner format, such as plain text or PDF, may help.
Step 9: Sign Out and Sign Back In
Authentication sessions can expire or become unstable. A user may still appear logged in, but Claude may not be able to complete actions correctly. Signing out and signing back in refreshes the session and can clear account-related glitches.
If the user signs in through a third-party provider, such as Google, they should make sure that account authentication is working normally. They may also need to allow pop-ups or cookies for the login process to complete properly.
Step 10: Check Usage Limits or Plan Restrictions
Claude may limit how many messages or high-demand requests a user can send during a specific period. If a usage limit has been reached, the interface may display a more specific notice, but some users may still encounter a general error during peak demand or near a limit.
The user should check account notifications, billing status, subscription details, and any visible usage messages. If the account has payment issues or plan restrictions, resolving those issues may restore normal access.
Step 11: Wait and Try Again Later
Sometimes the best fix is simply waiting. AI services can experience heavy traffic, temporary overload, or short-lived backend errors. If basic troubleshooting does not work and no local cause is obvious, waiting 15 to 60 minutes may solve the problem.
Users should avoid repeatedly submitting the same request every few seconds. Rapid retries can create additional errors or make it harder to identify whether the service has recovered. A calmer approach is to wait, refresh, and test with a short prompt.
Step 12: Contact Support
If the error persists for several hours or affects only one account, contacting support is appropriate. A useful support request should include the time the error occurred, the browser and device used, whether the problem happens in new chats, and any troubleshooting steps already attempted.
The user should avoid sending sensitive personal information unless it is required through a secure support channel. If a specific prompt or file causes the error, a short description of the task may be enough for support to investigate.
How to Prevent the Error in the Future
Not every instance of the Claude “This isn’t working right now” error can be prevented, but users can reduce the chances of seeing it frequently.
- Keep browsers updated to maintain compatibility with Claude’s interface.
- Use shorter prompts when working on complex tasks.
- Start new chats when conversations become very long.
- Limit conflicting extensions on browsers used for AI tools.
- Maintain a stable internet connection, especially during uploads.
- Check service status before assuming a local problem.
- Save important outputs outside Claude in case a session fails.
When the Error Is Not the User’s Fault
It is important to recognize that many instances of this error are not caused by anything the user did wrong. AI platforms depend on large-scale infrastructure, and occasional downtime or congestion is normal. Even a perfectly configured browser and strong internet connection cannot fix a server-side outage.
When the problem is widespread, the most effective response is to verify the outage, save any available work, and return later. If the error is local, the steps above usually identify the cause quickly.
FAQ
Why does Claude say “This isn’t working right now”?
Claude shows this message when it cannot complete a request. The cause may be a server outage, network interruption, browser conflict, overloaded conversation, file issue, or account limitation.
Is the error usually temporary?
Yes. In many cases, the error is temporary and disappears after refreshing the page, starting a new chat, or waiting for service conditions to improve.
Should a user clear cache and cookies?
Clearing cache and cookies is a good troubleshooting step if Claude loads incorrectly, fails repeatedly in one browser, or works on another device. It refreshes stored site data and can remove corrupted files.
Can browser extensions cause Claude errors?
Yes. Ad blockers, privacy extensions, script blockers, VPN extensions, and interface modification tools can interfere with Claude. Testing in a private window or disabling extensions can help identify the problem.
Why does Claude fail in one conversation but work in another?
A specific conversation may be too long, contain complex context, or include a problematic file. Starting a new chat with a shorter summary often resolves the issue.
Does a VPN affect Claude?
A VPN can affect Claude if it causes unstable connections, blocked regions, authentication issues, or suspicious traffic patterns. Temporarily disabling the VPN is a useful test.
What should a user do if none of the fixes work?
If the error continues after checking service status, refreshing, clearing browser data, switching browsers, testing the network, and trying a new chat, the user should contact support with details about the issue and troubleshooting steps already taken.
