Sub-posts and errors

Why sub-posts

One piece of material rarely goes out the same everywhere: on LinkedIn — in full, on Telegram — shorter and in your own words, on VK — with a different image. It can't be kept as one post: the texts differ, the times differ, the statistics too.

So the original material remains the flagship, and its versions live as sub-posts linked to the parent. In the calendar each stands in its own place, but it's visible that it's one story.

How they're counted

• Sub-posts don't participate in analytics totals — otherwise one story would be counted several times.
• Each sub-post's metrics belong to its channel and go into the channel breakdowns.
• A case gets the publications of both the flagship and its continuations.

Don't confuse a sub-post with a second channel in the same post. A second channel is the same text to another place, a sub-post is different text.

Custom text without a sub-post

If only the wording changes, not the substance, a sub-post isn't needed: in the editor each platform has its own text field. Empty — the shared text goes out, filled in — the custom one. The limit counter works the same way: it counts characters separately for each platform.

What “Error” means

An error always belongs to a channel, not the post as a whole. If a post went out on Telegram and failed on LinkedIn, it stays published, while LinkedIn has an error status with the platform's text. A post with the “Error” status is when no channel went out.

Common causes

• The platform token expired — reconnect the channel in settings, the error text will say exactly that.
• The platform didn't accept the material: text too long, unsuitable image, Instagram without an image.
• Channel not chosen: with several Telegram channels the service doesn't guess but asks you to choose explicitly.
• A connection drop with the provider — the publication may have gone through, see the next block.

How the service fixes itself

• On a connection drop the service re-asks the provider whether the post went out and substitutes the link instead of the error.
• If there's still no answer, the publication is retried once — duplicate protection on the platform side won't let a second post out.
• Once an hour failed channels are checked again: if the publication is found, the error is cleared on its own.
• And the other way round: if the service reported success but there's no post at the link, the channel is honestly marked as an error.

What to do by hand

1. 1Open the post and read the error text next to the channel — there's the cause, not a generic “didn't work”.
2. 2Fix it: reconnect the channel, shorten the text, add an image, choose a channel.
3. 3Run the publication again. Channels that already went out aren't republished — there'll be no duplicate.

If the post actually went out but the service lists it as an error, just paste the publication link into the channel card: the service accepts it and counts the post as published.