Answer: Use a smaller/final encode, avoid stacking huge parallel downloads, and retry when temp-media disk pressure clears. Prefer direct CDN URLs when possible. Check Status / /health during widespread failures.
Media requirements · Rate limits
What this means in a real publishing workflow
Large videos pass through temporary storage before destination upload. Failures can come from a configured byte limit, insufficient disk, a download timeout, or a source that reports one size but closes before all bytes arrive.
Recommended implementation
- Check the reported byte count and configured media limit.
- Confirm sufficient temporary disk space.
- Use resumable downloads and a timeout appropriate for the file size.
- Verify the completed file before beginning the platform upload.
How to verify the fix
Raising a size cap alone does not fix truncated downloads. The source must support stable transfer, and the downloader must detect incomplete byte counts before publishing.
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