Resolve pending, partial, failed and unknown social publications
Read destination-level evidence and recover deliberately without duplicating a post that may already exist.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Publishing activity → View destinations
PermissionAccess to the post; View all posts for wider workspace history; authorised provider access for verification
Before you begin
Open the existing request rather than recreating it immediately. One failed destination does not mean every network failed.
Follow these steps
- Read the overall request state, then open every destination row and its recorded reason.
- For Published, verify the provider account and final media processing. For Pending, keep the existing receipt and allow asynchronous reconciliation.
- For Skipped, correct unsupported content or destination eligibility in a separate draft. For Failed, address the specific provider error first.
- For Unknown, search the authorised provider account using content, time and remote references before deciding whether a replacement is necessary.
- Record the resolved outcome and create a replacement request only when you have established what the original did.
Fields and options
- 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.
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.
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.
Common questions
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.