I Automated Cross-Posting to 5 Platforms and Broke 3 Things

Description and use

Automated cross‑posting to five platforms caused three issues: shared draft collision, Markdown incompatibility, and silent rate‑limit throttling. Solutions are per‑draft database rows, per‑platform Markdown templates, and a cadence‑enforced scheduler.

Problem

Automating cross‑posting to multiple platforms caused failures due to shared mutable state, inconsistent Markdown rendering, and silent rate‑limit throttling.

Outcome

The pipeline now reliably publishes drafts to all five platforms without collisions, formatting errors, or silent throttling.

Workflow

• 1. Store each draft in a separate database row with a unique ID.
• 2. For each platform, apply a per‑platform Markdown template to the draft body.
• 3. Use a scheduler that ensures a minimum time gap between posts to the same platform.
• 4. Publish the formatted draft to the target platform via its API.

Evidence

The fix was boring and correct: drop the shared file entirely. Each draft now lives in a database row with its own id, and the publisher reads by id.

Source

The fix wasn’t a universal formatter. It was a per-platform template: the same body, but headers, fences, and tags rewritten to each site's dialect before send.

Source

The fix was a scheduler with a real cadence: each pair gets a minimum gap, and no two posts share an hour.

Source