Answer: Read Post History per platform. Retry only failed destinations. Do not re-fan-out successful ones. See Idempotency and Errors.
What this means in a real publishing workflow
Partial success is normal in multi-platform automation because every destination has separate credentials, media rules, rate limits, and processing behavior. Recovery must preserve successful results while correcting only failed branches.
Recommended implementation
- Store a separate Postifys ID for every platform branch.
- Mark published destinations complete and never resubmit them.
- Correct the failure reason for each failed destination.
- Retry failed events individually and reconcile the final campaign status.
How to verify the fix
Do not restart the entire fan-out workflow unless it first checks existing outcomes. Otherwise Facebook or Instagram may duplicate while YouTube is the only destination that needed repair.
Operational check: Test with one item, confirm the final destination and Postifys history state, and only then enable the recurring workflow. Keep the returned Postifys ID beside the source row so every result remains traceable.
Related Postifys resources
API documentation · Error reference · n8n automation guide · Safe retry guide · Compatibility matrix