Skip to main content

Social Media Automation

Resolve pending, partial, failed and unknown social publications

Read destination-level evidence and recover deliberately without duplicating a post that may already exist.

Reviewed 13 November 20262 minute read5 steps

Where to start
Publishing activity → View destinations

Fields and options

Access needed
Access to the post; View all posts for wider workspace history; authorised provider access for verification
Pending
Provider processing or a deferred final result is still being reconciled.
Unknown
An ambiguous external outcome cannot safely be treated as either an unsent or a confirmed post.
Partial
Some destinations succeeded while others did not. Inspect the rows, not just the aggregate label.

Before you begin

Open the existing request rather than recreating it immediately. One failed destination does not mean every network failed.

Follow these steps

  1. Read the overall request state, then open every destination row and its recorded reason.
  2. For Published, verify the provider account and final media processing. For Pending, keep the existing receipt and allow asynchronous reconciliation.
  3. For Skipped, correct unsupported content or destination eligibility in a separate draft. For Failed, address the specific provider error first.
  4. For Unknown, search the authorised provider account using content, time and remote references before deciding whether a replacement is necessary.
  5. Record the resolved outcome and create a replacement request only when you have established what the original did.

Check the result

Confirm the final account-level outcome for each destination. Check a replacement excludes destinations already published unless a second post is intentional.

If something does not look right

For permissions errors, verify/reconnect and complete provider review where required. For rate limits or outages, retain the original receipt and wait according to the provider response instead of repeatedly submitting.

Fields, rules and limits

  • Ambiguous external writes are not automatically retried.
  • Asynchronous checks are bounded; the module does not poll forever.
  • Deleting a private draft or disconnecting an account does not retract published provider content.

Questions and answers

Should I press Post Now again after a timeout?

First inspect the existing receipt and provider account. A timeout can occur after the network accepted the post.

Will the module delete a failed request’s successful posts?

No. Each destination is independent, and successful external posts are not automatically rolled back.

Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.

Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.