Relay PublishThe short answer
Describe one publication: the action, destination, expected outcome, exact message and time with timezone. Include a cleaned screenshot when helpful, but never a password, key or sign-in link containing a secret.
1. Isolate an example rather than mixing everything together
Choose the publication that demonstrates the problem. State whether it affects detection, preparation, account connection or sending to a particular network. A successful Facebook result and a failed YouTube result do not mean every destination failed. Describe them separately so the successful outcome remains a clear reference during the investigation.
Start with a factual sentence: “After approval, this video remains processing on this destination.” Mention additional affected videos afterward if relevant. The unpublished video guide helps identify the stage; the support request should then document what you observed rather than present an unverified explanation as the cause.
2. Keep the message and timing
Copy the exact message and any displayed error code. Note the action’s time with its timezone, such as 14:20 Europe/Paris, and when you checked the outcome. That distinction helps separate an immediate failure from processing that was still underway. Do not replace useful wording with a general description of something being broken.
Add Relay and iOS versions when available in your system information. Do not guess a version number. A confirmed public link may help, but it is not a reason to provide private account access. State the intended outcome too: a completed connection, prepared preview or visible publication. Different expectations can point to different stages.
3. Describe the path in a few actions
Write the steps you actually followed in order, without adding actions you did not perform. Say whether it happens consistently or only in this example. Mention relevant recent changes, such as a new destination, without sending the history of every account. One precise difference is more useful than an unstructured list of attempts.
“I select the video, approve YouTube and receive the following message. Facebook already has a confirmed link. I have not restarted the upload.”
This establishes the scope without inventing a diagnosis or suggesting that a successful publication needs to be repeated.
4. Clean screenshots before sharing them
Keep the relevant message and state visible. Hide unrelated personal addresses, confidential client content and unnecessary information. If a screenshot contains a password, key or complete OAuth link, do not send it unchanged. A broad screenshot can expose considerably more than the problem you intended to show to support.
Avoid sending the entire original video without being asked. Describe the issue first; an appropriate excerpt can be requested through the proper support channel if needed. Use the contact shown in the app or official Relay Publish website. Someone helping with an error message does not need your social account password to understand the observation.
5. Preserve successes during diagnosis
Before another attempt, check whether a final link already exists. Do not delete successful posts or reconnect every account merely to get a different screenshot. If you make a relevant new attempt, record its time and outcome so two events can be distinguished instead of silently replacing the original evidence.
The duplicate-prevention guide complements this precaution. Relay brings per-destination outcomes together to support clearer tracking without promising a universal resolution time. The public app is in preparation: join the waitlist to discover this iPhone workflow and distribution that is easier to understand when a specific action becomes necessary.
Put this into practice with Relay
Choose an authorized Instagram source, your destinations and whether to approve each video before publishing. Check compatibility before joining: the public iPhone app is in preparation.
Before you move on
- Identify one publication and workflow stage.
- Keep the exact message and timezone.
- Describe steps and expected outcome clearly.
- Remove secrets and unrelated data from screenshots.
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.