Why Does Facebook Keep Saying Something Went Wrong?

The short version: "Something went wrong" is Facebook's catch-all error message for dozens of unrelated problems, from a dodgy app cache to a shadow restriction on your account. There isn't one fix because there isn't one cause, so the quickest route is working through the likely causes in order of how common they are, starting with your own device before you ever assume you've been banned.

It's a lazy error message, and that's the actual problem

I'll say the uncomfortable bit first. Facebook's error message is deliberately vague because showing you the real cause (rate limit hit, content flagged, API timeout, account under review, server load) would require engineering effort Meta doesn't think is worth spending on a free product. You are not the customer on Facebook. Advertisers are. So when something breaks on your end, you get a message built for the lowest common denominator, not useful diagnostics. That's not a conspiracy, it's just priorities, and it means you have to do the detective work yourself.

I've watched this play out with small business owners trying to turn on reviews for their Facebook page and hitting the same wall posting a status update. Same message, completely different causes. That's the pattern worth understanding.

The five most common causes, ranked by likelihood

• 1. App or browser cache corruption - by far the most common, especially on the mobile app after an update.
• 2. Temporary server-side issues - Facebook's infrastructure does have regional outages and slowdowns, more often than they publicise.
• 3. Rate limiting - you've done too many of one action (posting, commenting, friending, joining groups) too fast and Facebook's spam system has quietly throttled you.
• 4. Content or account flags - something in your post, link, or image tripped an automated filter.
• 5. Permissions or settings conflicts - particularly common with Business Suite, linked Instagram accounts, or ad accounts with unresolved billing issues.

Worked example: say you run a local bakery page

Say you run a Facebook page for a local bakery and you're trying to post three times in ten minutes because you're behind on your content for the week: a photo, a price update, and a reply to a customer comment. The third action throws "something went wrong." That's not a bug, that's rate limiting. Facebook's systems can't tell the difference between an eager small business owner and a bot farm, so they slow you down the same way. Wait 20 to 30 minutes, do one action, and it clears. If you did the exact same three actions spread across the day, you'd never see the error at all.

Now compare that to a different bakery owner whose post keeps failing specifically when it includes a link to their online ordering site. That's not rate limiting, that's a link reputation flag, often tied to the domain itself having been reported as spam by someone else entirely, nothing to do with the bakery's own behaviour. Same error message, completely different fix.

The step-by-step before you panic

Work through this in order rather than randomly retrying the same action:

• Step 1: Log out completely, clear the app cache (Settings > Apps > Facebook > Storage > Clear Cache on Android, or offload and reinstall on iOS), and log back in.
• Step 2: Try the same action on a different platform entirely, desktop browser instead of app, or vice versa. If it works there, it's a device or app issue, not an account issue.
• Step 3: Check Facebook's own status via a third-party outage tracker like Downdetector. If thousands of other people are reporting it at the same time, it's server-side and there's nothing to fix on your end, just wait.
• Step 4: If it's isolated to one specific post, strip it back to plain text with no link and no image and try again. If that posts fine, add elements back one at a time to find the trigger.
• Step 5: If it's happening across every action, check Account Status in Settings for any policy notices you might have missed, because an account under review often throws this generic error instead of a clear warning.

When it's a posting restriction in disguise

This is the one people miss most often. "Something went wrong" sometimes isn't a technical glitch at all, it's Facebook's way of quietly blocking an action without telling you why, which is functionally identical to a restriction. If you've recently had a post removed, a comment reported, or you're posting the same link that got flagged as spam elsewhere, the system can throttle that specific action while leaving everything else working normally. I've written a full breakdown of this exact overlap in why Facebook won't let you post, because the two problems look identical from the outside but need different fixes.

The same logic applies to Business Suite and ad accounts. If you've got an unresolved billing dispute or a disapproved ad sitting in the queue, Facebook sometimes surfaces "something went wrong" on unrelated actions like scheduling a post, simply because the account itself is flagged. It's worth checking your ad account status even if the error happened on something that has nothing to do with ads.

Settings conflicts worth checking

A chunk of these errors come from settings interacting badly with each other rather than any single broken feature. If you've recently changed who can tag you, adjusted a take a break setting on a connection, or fiddled with tagging permissions, give it a few hours to propagate before assuming it's broken. Facebook's settings changes don't always apply instantly across every server, and trying the same action again ten minutes later sometimes just works because the change has caught up.

If you manage both a Facebook page and a linked Instagram account, a disconnect or re-authentication issue on one side commonly throws this error on the other. This is worth knowing if you're also trying to work out something unrelated-sounding like what "lead" means in Instagram chat, because cross-platform linking issues tend to surface as vague errors on whichever app you happen to be using at the time, not the one causing the problem.

What I'd try first, in practical terms

If I were troubleshooting this for a small business page with one error on one post, I'd clear the cache and try desktop first, that resolves the majority of cases in under five minutes. If it's happening on multiple actions across multiple days, I'd check Account Status before touching anything else. And if it's tied specifically to a link or an ad account, I'd assume it's a flag, not a glitch, and stop retrying the exact same thing, because repeated failed attempts on a flagged action can sometimes extend the restriction rather than clear it.

Facebook won't tell you which of these it is. That's the frustrating truth of managing any page or profile on a platform you don't own: you're troubleshooting blind, and the error message is designed for Meta's support load, not your understanding.

If that raises the next question, see Instagram Something Went Wrong: Fixes in the Order to Try Them.

This guide is part of my Facebook Help: 80 Guides to Pages, Groups, Ads, Stories and Fixes.

Frequently asked questions

Does "something went wrong" mean my account has been banned?

Not usually. A ban or suspension almost always comes with a specific notice in your Account Status section. The generic error is far more often a cache issue, a temporary rate limit, or a server-side glitch than an actual ban.

Why does the error only happen when I post a link?

Links get checked against Facebook's spam and safety databases before the post goes live. If the domain has been flagged, reported, or shortened through a service Facebook doesn't trust, the post can fail even though nothing is wrong with your account itself.

Will logging out and back in fix it?

For a large share of cases, yes, because it clears a corrupted local session or cache without you having to find and delete files manually. It's the fastest thing to try before assuming anything more serious is going on.

Should I keep retrying the same action if it keeps failing?

No, repeated retries on a flagged action can look like automated behaviour to Facebook's systems and make things worse. Change the content, switch platforms, or wait at least twenty minutes before trying again.