Relay PublishThe short answer
Read each destination’s status. A video may be waiting for your approval, uploading or processing on the network. Fix the specific cause before retrying only the affected upload.
1. Read the workflow, not just the thumbnail
Detection means a source post was found. Preparation retrieves and adapts available elements. Upload and destination processing follow. Final confirmation is a separate step.
Awaiting approval: your action is needed.
Sent / processing: the network has not confirmed yet.
Published: the destination confirmed the available result.
An overall status does not replace per-network results. Facebook may succeed while YouTube is still processing. Open the relevant destination’s details.
2. Check whether approval is required
Approval mode keeps videos waiting while you check captions, the cover and destinations. That is not a failure. Confirm the intended content before requesting another upload.
TikTok has specific steps for creator identity, available options, visibility and consent before transfer. In Relay, TikTok production remains subject to approval; Snapchat also awaits Public Profile access. Reconnecting cannot replace those external approvals.
3. Check destinations and permissions
A connected account is not necessarily a selected destination. Check the workspace name, source and publishing rule. For Facebook, find the exact Page; for YouTube, check the selected channel.
For expired access, use official reconnection. For an invalid session, restart the connection in the app rather than using an old link. Never share keys or tokens with support.
4. Check the file, then allow processing to finish
Inaccessible media, rejected formats or incompatible duration can block preparation. Captions and covers have their own constraints too. The exact error helps distinguish a content change, reconnection or waiting.
If the network received the video, processing time is not an immediate reason to upload a second copy. A temporary incident may need a later retry; an account restriction needs another action. Keep the rejection reason and time for diagnosis.
5. Retry failures, not successful publications
In tracking, open the final link when available. Preserve confirmed uploads. When a retry action is offered, target the failed destination and check that the underlying cause has been addressed.
Relay tracks outcomes and protects retries from duplicates within its workflow; this cannot guarantee a network accepts another attempt. If you also published manually, account for that before retrying. For persistent issues, contact support with the network, time and exact message, without secret information.
Before you move on
- Identify the waiting step and destination.
- Check approval and selected accounts.
- Fix the cause or allow processing to continue.
- Preserve successful publications before a targeted retry.
Official references
Platform rules can change. Check these sources for eligibility and technical constraints.
Practical guidance, not a promise of reach. Examples are illustrative. The Relay Publish public app is in preparation; platform access and permissions remain required.