Follow the work through its actual lifecycle
Publishing a video usually involves more than one operation. A tool saves your request, transfers or exposes a file, waits for platform preparation, and asks for the final publication. A network may then apply its own visibility or review rules. Different interfaces name these stages differently, so this guide explains the concepts rather than promising identical labels across all publishers.
Keep the distinction between the tool's record and the network's record clear. A local job ID helps support locate the request; it is not necessarily a public post URL. Likewise, a successfully transferred media object may exist without a finished post that references it. When an interface seems contradictory, ask which operation its status describes and what evidence confirms the next stage.
| Concept | What it establishes | What it does not establish |
|---|---|---|
| Scheduled | An intended future action is saved | The destination has accepted a post |
| Uploaded | Media bytes reached a service | The media is ready or public |
| Processing | The service is preparing the asset | A terminal failure |
| Awaiting native review | A person must complete a step | Automatic public release |
| Published | A post record or public result exists | Every viewer can access it or received an alert |
Use platform examples to interpret the boundary
Bluesky's video tutorial describes two upload paths. In the simple path, processing starts after the post is submitted, so a post can temporarily appear before its video is ready. The recommended preprocessing path waits for a video blob reference before creating the post. This shows why visible text without a playable clip is not automatically evidence that the entire publication failed.
TikTok's transfer guide distinguishes receiving all file parts from completing publication. A 201 transfer response means all parts arrived and TikTok can start posting; it is not itself proof of the finished public result. Its Upload workflow adds another boundary: the creator must open an inbox notification and continue in TikTok. Treat that as a handoff with an owner, not an unexplained delay.
When a post seems stuck, inspect before restarting
First record the last known stage, its timestamp, and the original operation identifier. Check the intended destination account directly. If a public post already exists, inspect whether the issue is playback, visibility, or stale reporting. If the media is still processing, consult the platform's current status and the publisher's supported waiting behavior. There is no universal processing deadline that applies to every file and service.
Do not submit a second copy simply because the first result is slow to appear in one interface. The first job may complete later. If a terminal error appears, preserve it and fix its cause before a narrowly targeted retry. If status cannot be resolved, ask support to inspect the existing operation. This is especially important when several networks already have successful copies of the same announcement.
Define completion for your own workflow
For each destination, record what counts as done: a public post with working video, a private review item delivered to a named editor, or a scheduled native release verified for the intended time. These are all legitimate workflow outcomes, but they are not the same promise. Tell collaborators which result they are responsible for and where to record proof of completion.
After release, save the destination URL, visibility, media result, and any unresolved issue. In Ferryman, review the specific flow's result and the native destination rather than extrapolating from a different platform's status wording. A simple completion log makes future debugging faster and reduces accidental duplicate submissions. It also prevents a marketing report from counting staged drafts as posts that actually reached an audience.
Sources & further reading
Written by Ferryman. Sources checked Oct 16, 2026. Platform rules can change; consult the linked documentation for current requirements.