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.
What happened
CivAll sent the post to the network. The network's automated review looked at it and refused it. Nothing was published, so there is no partial or duplicate post to clean up.
Because the network gave a definite answer, CivAll does not send the post again on its own. The post stays failed until someone publishes it again.
On TikTok this arrives as a spam risk decision. On Facebook and Instagram it usually arrives as a message about the post looking like spam or the account posting too often.
Why it happens
Every network runs automated checks on posts that arrive through an app. Those checks look at patterns, not at who you are. It is an automated judgement, not a review of your agency, and no person at the network read your post before it was refused.
In practice the things that set it off most often are:
- The same or nearly the same wording published repeatedly, which is common with recurring reminders and standing notices.
- Several posts sent from one account in quick succession.
- Shortened links, or links to a domain the network does not recognize.
- Wording that reads like bulk marketing, such as heavy capitalization, repeated punctuation, or urgent calls to act now.
- The same photo or video reused across many posts.
These are thresholds, and networks change them without notice. A post worded the way you have always worded it can be flagged this month and not last month.
What to do
- Wait before trying again. Sending the identical post a minute later usually gets the identical answer.
- Change something about the post. Rewrite the opening line, shorten it, or swap the image or video. Small changes are usually enough.
- Replace any shortened link with the full address of the page you are linking to.
- Publish again.
If the message is time sensitive, publish it directly on the network instead of waiting for a retry to succeed.
What does not help
Reconnecting the account does not help here. The connection is working. The network accepted the request and then refused the content. Reconnecting fixes a different failure, described in Publishing failed: reconnect the account.
Publishing the same post again immediately does not help either. The same automated review runs on every attempt.
Contacting the network is rarely productive for a single refused post. There is normally no way to ask for a second look at one automated decision. Changing the post and trying again is faster.
If it keeps happening
If several posts in a row are refused on one account, space your posts further apart and vary the wording between them. Scheduling posts across the day rather than sending a batch at once helps.
If every post to one account is refused while the same content publishes fine on your other accounts, the issue sits with that account on that network. That is worth raising with the network directly, because it is not something CivAll can change.
If the failure message mentions the video, image, or file rather than the post as a whole, read Publishing failed: the media was rejected instead. If it names a specific thing in the post such as a tag or a collaborator, read Publishing failed: the network rejected the post.