Draw the route before enabling automation
Write every publishing connection as an arrow from a specific source account to a specific destination account. Include every tool, native schedule, and manual handoff involved. A platform name alone is not enough when you manage multiple brands. The map should explain how one original becomes each intended copy and whether any copy can be read again as a new source post.
An illustrative loop is account A sending to B while another workflow sends B back to A. Another duplication pattern has A sending directly to C and also reaching C through B. Whether a product actually repeats those posts depends on its filtering and deduplication behavior, so a diagram identifies risk rather than proves an incident. Do not assume independent tools share a record of what has already been sent.
Prefer a simple route with one owner per copy
For a small creator workflow, one chosen origin distributing to selected destinations is easier to reason about than an interconnected web. You can still write native posts elsewhere, but decide whether those posts should trigger distribution. Keep separate editorial streams explicit. If two people use different publishers for the same account, assign ownership by destination and campaign before either schedules a release.
The route examples below are design checks, not a description of every Ferryman configuration. A loop is not made safe merely by inserting a delay. Nor is matching text a perfect identity test: legitimate posts can share wording, while the same idea can be transformed during distribution. Ask your tool how it distinguishes an original, a copied post, and a retry, particularly across different workflow types.
| Route pattern | Question to ask | Simpler arrangement |
|---|---|---|
| A to B, then B to A | Can imported copies trigger the reverse rule? | Choose one origin for this stream |
| A to C and A to B to C | Who owns C's copy? | Keep one path to C |
| Native schedule plus automatic sync | Will native publication trigger another copy? | Assign one executor per destination |
| Manual retry plus unresolved job | Could the original still complete? | Reconcile the existing operation first |
Investigate duplicates before cleaning them up
Pause the route most likely to create additional copies using the tool's supported controls. Save the duplicate URLs, creation times, source records, and job identifiers. Compare which copy appeared first and whether it became a new origin event. Do not delete all evidence immediately; the ordering can explain whether this was a feedback loop, a duplicate schedule, or a manual recovery after an ambiguous result.
Distinguish media deduplication from post deduplication. Bluesky documents that a video already processed by its service can return an existing blob reference. Reusing that media object does not by itself establish that a post already exists or prevent a publisher from creating another post referencing it. The important check is the destination post identity and the operation that created it, not merely whether file processing was reused.
Restart with a controlled, traceable test
After correcting the route map, use one harmless original with a recognizable label and observe all intended destinations. Verify that each receives one copy and that no copied post returns through another path. Wait for the relevant processing and handoff stages to resolve before declaring the route stable. A single test cannot prove every future edge case, but it can expose a basic circular configuration.
Then remove unintended duplicates deliberately, preserving the preferred public copy and updating any links you control. Keep the route map with your weekly publishing checklist and revisit it when adding a platform or another tool. Ferryman's create, schedule, and sync workflows should be evaluated as the actual paths you use; never infer cross-tool deduplication from a product name or a successful one-platform test.
FROM GUIDE TO WORKFLOW
Explore this workflow in Ferryman
Configure automatic cross-posting routes
Review Ferryman's origin-to-destination flows, opt-out controls, and handling of Ferryman-created posts. Keep routes owned by other tools in your own route map.
Sources & further reading
Written by Ferryman. Sources checked Oct 16, 2026. Platform rules can change; consult the linked documentation for current requirements.