Why Your Facebook Group Post Failed: Blocked or Just Refused?

Most Facebook group posts that fail are not "Facebook jail." They are a single group refusing a single post — and the difference decides whether you should stop everything or just move to the next group. Facebook returns a numeric error code for almost every refusal, and those codes separate cleanly into two categories: an account-level block that applies everywhere and gets worse if you keep going, and a per-group refusal that means nothing beyond that one community's rules. Marketers routinely mistake the second for the first, panic, and stop posting for a week they didn't need to lose. Others mistake the first for the second, keep posting into a deepening block, and turn a 24-hour restriction into a real one. This page decodes every code we see in production and tells you which of the two you're looking at.

The Facebook group posting error code decoder

This is the full map we classify against in production, with the response each code should trigger. If you only take one thing from this page, take the "What to do" column — the codes matter because the correct reaction differs so sharply between them.

Code	Facebook's meaning	Scope	What to do
1390008	Account-level action block — "you can't use this feature right now"	Whole account	Stop posting now. Wait it out. Do not retry
368	Temporarily blocked for policy violations (pairs with 1390008)	Whole account	Stop posting now. Meta's own guidance is to wait and retry later
1373034	Insufficient permission (error subcode)	One group	Skip this group. Nothing is wrong with your account
1675030	Insufficient permission (error code)	One group	Skip this group. Check whether you're posting as a Page
190	Invalid or expired OAuth access token	Session	Log in again. No penalty attached
102	Login status or access token expired, revoked or invalid	Session	Log in again
1348131	Token expired	Session	Log in again
1404006	Session invalid	Session	Log in again
1357001	Not authorized	Session	Log in again; re-check which identity you're acting as
1357004	Checkpoint — Facebook wants to verify it's you	Session	Open Facebook and clear the checkpoint before doing anything else
1357032	Stale or actor-mismatched request token	Identity	Reload Facebook. Usually means your acting identity changed mid-session
1357006, 1357007	Actor mismatch variants	Identity	Same — reload and confirm who you're posting as
2207001	Persisted-query / doc_id rotation	Tooling	Not your fault. Facebook changed an internal identifier; your tool needs updating
4, 17	Too many calls (API-level throttling)	Rate	Slow down. Meta's guidance is to pause and reduce frequency

Codes 190, 102, 368, 4 and 17 are documented in Meta's official error-handling reference, and several are corroborated in vendor troubleshooting docs from Agorapulse, ContentStudio and Smash Balloon. The longer seven-digit codes are the ones Facebook's own web surfaces return, and the group-posting interpretations above come from classifying them across our own fleet.

Blocked or refused? The only distinction that matters

Every code in that table collapses into one of two situations, and confusing them is the most expensive mistake in group marketing.

A refusal is local. One group said no. Its rules might forbid links, or promotional posts, or posts from Pages, or posts from members who joined less than a week ago. Your account is completely healthy. The correct response is to move to the next group without breaking stride — and if you stop your whole run over it, you've lost the day's reach for nothing.

A block is global. Facebook has decided your account is posting too fast or too repetitively and has suspended the feature everywhere. The correct response is the exact opposite: stop immediately. Every additional attempt while a block is live is another data point confirming the behaviour Facebook flagged, and blocks escalate. A 24-hour restriction that you argue with becomes a longer one.

The account-level block: 1390008 and 368

This is the one people mean when they say "Facebook jail." Facebook's user-facing wording is some variant of "You can't use this feature right now" or "It looks like you were misusing this feature by going too fast", and the machine-readable form is error 1390008, often paired with api_error_code 368. Meta documents 368 as a temporary block for policy reasons and its stated remedy is simply to wait and retry the operation.

What triggers it, in rough order of how often we see it:

• Speed. Too many actions in too short a window. This is the dominant cause and the easiest to fix.
• Repetition. The same text posted into many groups. Identical content across destinations is the classic spam signature — see how to avoid duplicate post flags.
• Cold-start volume. A new or long-dormant account behaving like an established one. Accounts have an implicit trust level, and it is earned over time.
• Negative feedback. Group members reporting or hiding your posts. This one compounds quietly.
• Link patterns. The same destination URL repeated across many communities in a short window.

Three things not to do when you see it. Don't retry — every attempt during a live block reinforces it. Don't switch to another tool and continue — the block is on the account, not the software, so this only adds attempts. Don't create a second account to keep going — evading an enforcement action is a far more serious violation than the pacing problem that caused it, and it puts the original account at risk too.

What to do instead: open Account Status in Facebook's settings, which shows your actual restrictions and their real end dates rather than the internet's guesses. Then stay off automated posting entirely until it clears, and come back at a lower volume than before. Our guide to group posting limits covers the pacing side in detail.

The per-group refusal: 1373034 and 1675030

Here is the finding that surprised us most when we audited our own failure classification: this category, not account blocks, is the single largest bucket of failed group posts in our fleet. In a one-off internal review of unclassified failures, roughly seven in ten turned out to be this permission refusal, and about two thirds of the events that had been reported as engine errors were the same thing. It had been carrying no error code we recognised at the time, so it was landing in a catch-all bucket and being read as a bug in our software. It was not a bug. It was groups enforcing their own rules, exactly as designed.

These figures are directional and come from our own aggregated, anonymised counts rather than from Meta. We're publishing them because the shape of the finding matters more than the decimal places: if your group posts are failing, the overwhelmingly likely explanation is the groups, not your account.

Facebook returns "Insufficient permission" for a whole family of ordinary situations:

• The group requires admin approval for every post and yours is queued, not rejected.
• The group forbids links, or promotional content, or the post format you used.
• You have a membership waiting period — some groups block posting for the first days after you join.
• The group is archived or read-only, or has been set to admin-only posting.
• You were muted in that group specifically, which looks identical to a permission error from the outside.
• The Page trap, below — the one that catches serious marketers most often.

The Page trap

A large share of these refusals are one specific, fixable thing: you are posting as a Page into a group that only accepts posts from personal profiles. Facebook returns the same generic "Insufficient permission" it would for any other rule, so it reads like a mysterious failure rather than the simple identity mismatch it is.

The fix is either to switch to your personal profile for that group, or to ask the admin to enable Page posting. What makes this worth calling out is that it fails silently and consistently — a marketer who switched to Page posting for brand reasons can lose a large fraction of their group reach and never learn why. If you post as a Page, audit which of your groups actually accept it. Our notes on group management and the automatic approval explainer cover the surrounding mechanics.

Session and authentication errors: 190, 102 and friends

These are the friendliest errors on the list, because they carry no penalty at all. Codes 190 and 102 are Meta's documented "your token is expired, revoked or invalid" family; 1348131 and 1404006 are the equivalents Facebook's web surfaces return; 1357001 means the request wasn't authorised in the first place.

Nothing is wrong with your account. Log in again and continue. The one that deserves separate handling is 1357004, a checkpoint — Facebook wants to verify it's really you, usually after an unusual login, a password change, or a device it hasn't seen. Clear it manually in Facebook before resuming anything automated. A checkpoint left unresolved while software keeps trying looks precisely like an account someone else is driving.

One useful rule for anything that touches tokens: a 190 is terminal, not transient. Retrying it produces the identical failure and burns your rate budget on the way. Re-authenticate rather than retry.

Actor mismatch: 1357032, 1357006, 1357007

These mean Facebook received a request signed for one identity while the session is now operating as another — you switched between your personal profile and a Page, or had Facebook open in several tabs acting as different identities, and the request token went stale.

It is harmless and fixed by reloading Facebook. It matters mainly because of what it can cause if handled badly: a tool that retries blindly through an actor mismatch can end up posting under the wrong identity, or posting twice. If you manage multiple Pages and a personal profile, keep one acting identity per browser session and let runs finish before switching. This is the same identity plumbing behind a class of confusing "wrong account posted" reports.

2207001: when Facebook moves the furniture

2207001 signals a rotated persisted-query identifier — an internal reference Facebook uses for its own web requests, which it changes without notice. When it rotates, tools built on the previous value fail until they're updated.

This one isn't your fault and there's nothing to fix on your account. It's worth knowing about only because it explains a specific pattern: a posting tool that worked yesterday and suddenly fails for everyone at once, with no change in your behaviour. That's a signature of platform-side rotation, not a restriction. The relevant question for any tool you rely on is how quickly it can push a fix when this happens — we describe our own approach on the status page.

"My post vanished" — usually not an error at all

A large share of "my group post failed" reports involve no error code whatsoever, because the post succeeded and then wasn't visible. Four distinct things get confused here.

Pending admin approval

The most common by far. The group requires approval, your post is sitting in the moderation queue, and it will appear when a human gets to it — which can be hours or days. Check the group's "Your posts" or pending view before concluding anything failed. Nothing is wrong.

Flagged as spam inside the group

The post was created but marked as spam by the group's own filtering or admin tooling. It exists but members aren't seeing it. This is group-level moderation, separate from any Facebook account restriction, and the remedy is editorial: fewer links, less promotional framing, more genuine contribution.

Removed by an admin after publishing

It went live, an admin removed it. No code, no notification in most cases. If this happens repeatedly in the same group, re-read the rules — repeated removals often precede a mute or a ban from that community.

Published, but with something dropped

The post landed while an attachment, a background colour, or a link preview didn't. The post is real; the formatting isn't what you intended. Worth checking before you republish, because republishing a post that actually succeeded is how a formatting annoyance becomes a duplicate-content problem.

That last point generalises into the most important operational rule on this page: never retry a post you haven't confirmed failed. A false failure followed by a retry produces a duplicate, duplicates produce spam signals, and spam signals produce the account block you were trying to avoid. Confirming success before retrying is the difference between a resilient posting workflow and one that manufactures its own restrictions.

Why reading the error message instead of the code silently fails

This is a technical point with a very practical consequence, and it's the kind of thing that only becomes visible at fleet scale.

Facebook localises its error text. A Spanish-language account gets "no puedes usar esta función"; an Arabic-language one gets the Arabic equivalent; an English one gets "you can't use this feature right now." The numeric code is identical in every language.

Any tool — or any human troubleshooting guide — that decides what happened by matching English words will therefore work correctly for English users and fail silently for everyone else. In the failure mode that matters most, an account-level block on a non-English account reads as an ordinary per-group skip, so the software keeps posting into a deepening block, and the protective stop never fires. That's not a cosmetic bug; it's the difference between a 24-hour restriction and a serious one, and it lands specifically on international users.

The rule that follows is simple and worth applying to your own troubleshooting: classify on the number, never on the prose. If you're evaluating a posting tool, it's a fair question to ask how it detects an account block, and whether that detection works when Facebook is set to a language other than English.

How long do Facebook posting restrictions last?

Short blocks generally clear within 24 hours to a few days, and longer ones escalate from there with repeat incidents. You'll see confident-sounding tables across the web claiming precise durations — 24 hours, then 3 days, then 7, then 30 — and they disagree with each other because Facebook does not publish a fixed schedule for these action blocks. Meta does publish a strike system for Community Standards violations, but that's a different mechanism from the pacing-driven feature blocks group marketers actually hit.

Rather than trusting any published number, including ours: open Account Status in your Facebook settings. It shows the restrictions actually on your account and when they end. That is the only authoritative answer for your specific case, and it takes ten seconds.

What reliably makes it worse is continuing to act during the block. What reliably makes it better is time plus a genuine change in behaviour afterwards — because a second block arriving soon after the first is treated as a pattern rather than an accident.

How to not get blocked in the first place

Everything that prevents an account block comes down to looking like a person rather than a process.

• Vary every post. The same text in thirty groups is the single strongest spam signal available. Rewrite per destination — spintax and AI rewriting both do this, and the duplicate post checker tells you whether two versions differ enough to matter.
• Spread the run. Posts distributed over hours read as normal activity; posts fired at one timestamp do not. Timing research helps you pick the window.
• Warm up new accounts. Start low and build. Trust is earned, and volume that's fine on a two-year-old account is not fine on a two-week-old one.
• Rest overnight. Continuous round-the-clock activity is not a human pattern.
• Prune groups that always refuse. If a group has rejected you ten times, it will reject you the eleventh. Removing it costs nothing and improves every metric you care about.
• Contribute, don't only broadcast. Negative feedback from members is an input to enforcement, and the cheapest way to reduce it is to be a participant in the communities you post to.

These are also the principles behind our account safety layer — randomised pacing, a live protection score, night mode, warm-up and an adaptive slow-down as daily volume rises. The full reasoning, including the honest limits of what any tool can promise, is on the security page and in is using a Facebook auto poster safe?

Frequently asked questions

Why did my Facebook group post fail?

In the large majority of cases, because that specific group refused it — its rules forbid the post type, it requires admin approval, or you are posting as a Page into a group that only allows personal profiles. Facebook reports this as "Insufficient permission", error 1373034 or 1675030, and it says nothing about the health of your account. Only errors 1390008 and 368 indicate an account-level block that affects every group.

What does Facebook error 1373034 mean?

It is Facebook's "Insufficient permission" subcode, returned when a group declines your post. Common causes are a rule against links or promotional content, a required admin approval step, a membership waiting period, or posting as a Page into a group that only accepts personal profiles. It is specific to that one group, so the correct response is to skip it and continue posting elsewhere.

What does Facebook error 1390008 mean?

It is Facebook's account-level action block, usually shown as "You can't use this feature right now" or "we limit how often you can post", and it often appears alongside api_error_code 368. It applies to your whole account rather than one group, and it is typically triggered by posting too fast, posting identical content repeatedly, or high activity on a new account. Stop posting immediately, because further attempts during a live block make it longer.

What is Facebook error code 368?

Meta documents 368 as a temporary block applied for policy reasons, and its official guidance is to wait and retry the operation later. In group posting it pairs with 1390008 and means the same thing: an account-wide restriction on the posting feature, not a problem with any individual group.

What does "Insufficient permission" mean on a Facebook group post?

It means the group did not accept the post. That covers a rule against your content type, a pending-approval requirement, a waiting period for new members, an archived or admin-only group, being muted in that community, or posting as a Page where only profiles are allowed. Your account is unaffected and posting elsewhere will work normally.

Why can't I post in a Facebook group as my Page?

Many groups accept posts only from personal profiles and not from Pages. Facebook returns the same generic "Insufficient permission" error it uses for every other rule, so the cause is not obvious from the message. Either switch to your personal profile for that group or ask an admin to enable posting by Pages. Marketers who move to Page posting for branding reasons often lose a large share of their group reach this way without realising why.

How long does a Facebook posting block last?

Short blocks commonly clear within 24 hours to a few days, and repeat incidents escalate from there, but Facebook does not publish a fixed schedule for these action blocks. Published duration tables disagree with each other for that reason. The reliable answer for your own account is in Account Status in your Facebook settings, which shows your actual restrictions and their real end dates.

Is Facebook jail the same as a group refusing my post?

No, and confusing them is expensive in both directions. Facebook jail is an account-level block that applies everywhere and gets worse if you keep posting. A group refusal is one community enforcing its own rules while your account remains completely healthy. Stopping a whole campaign over a group refusal wastes reach you did not need to lose, and continuing to post through a real block turns a short restriction into a long one.

Should I retry a failed Facebook group post?

Only after confirming it actually failed. If the post reached the group and you republish it, you create a duplicate, and duplicates are one of the strongest spam signals Facebook acts on. Retrying is also the wrong response to an account-level block, where each attempt reinforces the restriction. For a per-group refusal there is nothing to retry, because the group's rules will produce the same result.

My post is not showing in the Facebook group — was it blocked?

Usually not. The most common explanation is that the group requires admin approval and your post is waiting in the moderation queue, which can take hours or days. Other possibilities are that the group's spam filtering hid it, that an admin removed it after publication, or that it published while an attachment or link preview failed. Check the group's pending posts view before assuming a failure, and do not republish until you have.

What do Facebook errors 190 and 102 mean?

Both mean your login session or access token has expired, been revoked, or become invalid. They are not restrictions and carry no penalty. Log in to Facebook again and continue. Retrying without re-authenticating produces the identical error, so re-authentication rather than retry is the correct response.

What is a Facebook checkpoint error?

Error 1357004 means Facebook wants to verify your identity, typically after an unusual login, a password change, or a new device. Open Facebook and complete the verification manually before resuming any automated activity. Leaving a checkpoint unresolved while software continues to send requests resembles an account being operated by someone else, which is worse than the original prompt.

Why does my posting tool suddenly fail for everyone at once?

That pattern usually indicates error 2207001, a rotated persisted-query identifier. Facebook changes these internal references without notice, and tools built on the previous value fail until updated. It is not caused by your account or your behaviour, and there is nothing to fix on your side beyond waiting for the tool to ship an update.

Why do error messages matter less than error codes?

Because Facebook translates its error text into the account's language while the numeric code stays identical worldwide. Any troubleshooting method that matches English words works for English users and fails silently for everyone else. The dangerous case is an account-level block on a non-English account being read as an ordinary per-group skip, so posting continues into a deepening restriction. Always classify on the number.

Sources

• Meta — Graph API error handling reference (codes 190, 102, 368, 4 and 17, and Meta's stated remedy for each)
• Meta Transparency Center — Restricting accounts and Counting strikes (the strike system, and Account Status as the authoritative view of your own restrictions)
• Agorapulse — Common publishing errors (368 / 1390008 observed as a rate and repetition block)
• ContentStudio — Facebook errors while publishing (token and session error handling)
• Smash Balloon — Facebook API error message reference (independent corroboration of the token error family)
• Meta — Graph API rate limiting (throttling codes 4 and 17)

The seven-digit codes and the group-posting interpretations above come from Group Posting's own production error classifier. Fleet figures quoted are directional, drawn from a one-off internal review of aggregated, anonymised failure counts, and are labelled as such wherever they appear — they are not Meta figures and are not presented as precise measurements.

Keep going

• Facebook group posting limits explained — the pacing side of avoiding a block
• What causes Facebook posting restrictions — the behavioural triggers in more depth
• How to avoid duplicate post flags — the repetition half of the problem
• Is using a Facebook auto poster safe? — where the real risk actually sits
• Facebook Groups API in 2026 — why cloud tools can't post to groups at all any more
• How to mass post to Facebook groups safely — the workflow this all supports
• Account safety features · Security and privacy · Pricing