Claude FAQ: How to handle failed sends, missing projects, and permission prompts

The most frustrating thing about using Claude isn’t not knowing how—it’s when messages suddenly won’t send, you get a “no permission” prompt, or you can’t see your history. Below, we break down common Claude issues by scenario. Following these steps usually helps you pinpoint the cause within minutes. If the page shows a more specific error message, defer to what’s displayed in the Claude interface.

Claude message failed to send or keeps spinning

If Claude shows a send failure, first switch networks and try again: move from a company/campus network to a mobile hotspot to quickly rule out gateway blocking. Then refresh the page or reopen the app, and split the same content into two messages to avoid triggering an error due to overly long input.

If Claude still keeps spinning, try clearing your browser cache and disabling script-type extensions (ad blockers and privacy extensions can sometimes interfere with requests). Also, asking questions very frequently in a short period may trigger rate limiting—waiting a few minutes and sending again usually restores it.

Claude repeatedly verifies on login, jumps back to the homepage, or shows an error

If Claude gets stuck in a login verification loop, first confirm your system time and time zone are correct—time drift can cause login token validation to fail. Then try signing out and signing back in, or log in once in an incognito window to see whether there’s a local cookie conflict.

If Claude shows “Unable to complete request / session expired,” it’s most likely due to an unstable network environment or inconsistent proxy settings causing redirect issues. Keep the same network egress and avoid frequently switching between Wi‑Fi and mobile data during login.

Claude Projects can’t be found, or history doesn’t display

If your Claude project or conversation “disappears,” first check whether you switched to the wrong account or workspace; many people use email aliases or third-party sign-in and end up in a different account. Then check filter/search conditions—sometimes it’s just accidentally filtered to “Recently used.”

If Claude behaves inconsistently across devices, refresh on the original device and wait for syncing to complete, then check on the other device. If the missing data persists, don’t keep creating new projects—keeping screenshots of existing information is more helpful for follow-up troubleshooting.

Claude file upload failed, format not supported, or parsing incomplete

If Claude upload fails, first confirm whether the file format and size match what the page indicates; different entry points may allow different upload types. Renaming the file using English letters/numbers and avoiding overly deep paths can also reduce recognition issues.

If Claude can upload but doesn’t parse the content fully, export to a more universal format (for example, convert scanned documents into copyable text), or split long documents into sections and upload them separately. If needed, specify in your message “use page X as the reference” so Claude can align the context better.

How to self-check when Claude says you don’t have permission or content is blocked

If Claude shows no-permission or content-blocked messages, first check whether certain restriction settings are enabled in the project, or whether the current conversation context contains sensitive snippets that cause the whole request to be rejected. Rephrase the question, remove irrelevant sensitive words, and describe the purpose more clearly—this often gets it through.

If Claude still can’t recover, record three pieces of information: the exact prompt text, the steps to reproduce, and whether it still reproduces after switching networks/devices. Submitting these details via the official support channel will be faster to diagnose than simply saying “it doesn’t work.”