My post didn’t go out

First: you hear about it

A post that does not go out is not a notification you find somewhere in a screen tomorrow. You get an email, with the post in it, the reason, and what the next step is.

What happens by itself

Not every error is the same. A platform that is briefly overloaded is something other than a text that gets refused.

• On a temporary error Ploffo tries again: up to six attempts, with gaps that grow to six hours — a fixed schedule, regardless of what wait time the platform itself gives.
• You do not get an email per attempt. You only hear about it if it still has not worked after the last one.
• Nothing is ever published twice. Only one attempt works on a post at a time, and before a new one starts, the channel itself is checked for the post. So a post that did go through but whose answer got lost does not end up online twice.
• On a permanent error there is no retry. A refused text does not get better on a second attempt.

The three causes that come back most

The channel came loose. A password that changed, a page that changed owner, or a token that expired. You see it on the channel itself in the app, and you reconnect it. See Connecting channels.

The platform refused the content. Then it is about the image or the text, not about the connection. See Image or text rejected.

The permissions are no longer enough. You are still connected, but your role on the page has changed. Platforms only let administrators publish, not editors.

And the post itself?

It stays where it was, with its text and its image. You change what needs changing and put it back in the queue — nothing has to be remade.