CivAll
Support
Knowledge Base
Contact
Social media management for local government
How-to guides
What CivAll Social is, how access works, and your first steps.
2 articles
The composer, media, scheduling, queues, templates, and post history.
14 articles
The calendar, drag-to-reschedule, and post previews.
6 articles
Review workflows that keep posts safe before they go public.
4 articles
Connecting and reconnecting your social media accounts.
1 article
Comments, messages, sentiment, and moderation in one place.
5 articles
Monitoring content from your accounts, public sources, and RSS.
Post analytics, Custom Reports, and scheduled report emails.
Inviting people, permission sets, and departments.
Pausing everything when something goes wrong, and resuming safely.
Fix a problem
Facebook has put an identity check on this Page or profile. Publishing stays blocked until someone completes it on Facebook itself. Reconnecting the account in CivAll does not clear it.
A post can fail because the connected account is missing a role or permission the network requires in order to publish. The connection itself is fine. Reconnecting helps only when the person signing in holds the role that is missing.
A post can fail because the connection between CivAll and the social account is no longer valid. The network will not accept posts on that account's behalf until someone signs in again. Reconnecting the account fixes it.
The network refused this post because the account has published too much in too short a time. Nothing is wrong with the post itself. Every network sets its own limit and its own reset, so the wait depends on where you were publishing.
The post did not go out because the network's automated review flagged it. This is a machine decision made by the network, not a review of your agency. Waiting a while and changing the wording or the media usually clears it.
The network received the post and refused it for a specific reason that is not spam. The two common causes are a tagged or collaborating account that does not accept invites, and a post built in a way the network does not support. Both are fixed by editing the post and publishing again.
The network turned down the photo or video on this post, or a detail attached to it. The post did not go out. Adjusting the file or the details and publishing again is normally all it takes.
The network stopped responding partway through publishing, so CivAll cannot tell whether the post went out. Check the account on the network before you publish again. Publishing again is how the same post ends up on your page twice.
Sometimes a connected account stops working because its authorization to the platform broke — it’s “detached.” Reconnecting (reattaching) restores it. This article explains why it happens and how to fix it.
Help and answers for the CivAll civic engagement platform — publishing, archiving, websites, and more.
Search
System status
support@civall.com
Contact the support team
civall.com
© 2026 CivAll · Social News Desk