Answer: Check /health, open Post History for the job, wait for provider processing on YouTube/Meta, and for TikTok complete the inbox publish step.
What this means in a real publishing workflow
A post can remain processing while Postifys downloads media, refreshes credentials, uploads a large file, or waits for the destination provider. The correct response depends on the recorded stage and whether progress is still changing.
Recommended implementation
- Check Post History for the current stage and last update.
- Verify service health and available storage.
- Allow long YouTube uploads enough time to complete.
- Retry only after the event becomes failed or an operator confirms the worker stopped.
How to verify the fix
Do not submit the original content again while the first event is queued or processing. A second request can produce a duplicate if the first provider operation eventually succeeds.
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