Open the Final stage
After publishing, open the post’s QA & APPROVE tab and inspect Final. The destination tiles show the channels where delivery has been recorded and link to the actual post when a URL is available.
Read each destination independently. Publishing to several channels is not a single all-or-nothing event; one provider may accept a post while another rejects it.
Verify the public result
- Check the destination name and profile.
- Read its delivery status.
- Open the recorded post link.
- Confirm the copy, image and article link as a visitor.
- Compare the actual result with the approved version.
A missing post URL is not a reason to invent one from a profile address. Use the provider identifier and recorded status to investigate, or check the provider directly.
Recover a failed destination
Read the error before retrying. Common prerequisites include valid authorisation, eligible account access, an available image, permitted text length and a ready source article.
Repair the specific condition, then use the supported retry action for the failed destination. Keep successful results intact. Repeating delivery to every destination can duplicate posts that already exist.
Treat uncertain outcomes carefully
A timeout or interrupted response can leave uncertainty about whether the provider accepted a submission. Inspect the provider and delivery history before retrying. An uncertain result is different from a clear rejection.
Disconnecting a profile, deleting a planning campaign or editing the local draft does not automatically remove a remote post. If a published post needs correction or removal, use the supported workflow or the provider’s own controls and verify the public result again.
Standard delivery covers text and a single shared image. Reels, Stories, carousels and other expanded formats are planned capabilities, so they should not be inferred from a successful standard post.