Relay PublishThe short answer
Identify the affected account and workspace, keep your rule details, then start a connection from Relay. Review the authorized identity and destinations after returning. Reconnecting does not approve a video waiting for your decision.
1. Separate an expired account from an unavailable service
Read the full message and note the network involved. If every screen fails to load, the issue may concern your Internet connection or the service. If only one account requests action while others respond, begin with that specific access instead of changing the whole configuration.
An account saved in an app and an authorization that still works are not the same thing. Google documents several situations in which tokens stop working. This explains the principle of reconnecting; it does not prove that every Relay error comes from expiration or from the same network.
2. Find the correct workspace and existing rule
Before changing anything, check the active workspace and note the source, destinations and approval mode. A screenshot of this configuration can help you review it afterward. Do not confuse the profile granting access with a Page or channel chosen as the publishing destination.
For a client, check that you still hold the necessary rights on their account. Switching Relay workspaces does not grant additional network permissions. The guide to separate publishing workspaces helps keep these contexts distinct while you investigate. Keep the original configuration understandable before attempting a repair.
3. Start a fresh connection from Relay
Use the affected account’s connection flow in Relay, then read the identity displayed by the network. The browser may already be signed in to another profile. Authorize the correct account and necessary resources rather than reusing an old link from a previous attempt.
You manage a brand in its own workspace, but the browser shows your personal profile. Check the final Page or channel instead of recognizing only the photo of the profile granting authorization.
If you cancel or the session expires, start again from the app. Never share a password or access token in a support request.
4. Review the result before retrying videos
After returning, check the account name, whether reconnection is still required and which resources were actually authorized. Review the rule instead of assuming the first account displayed is the right destination. Keep other working connections intact unless a specific issue affects them.
Next, inspect video states: pending approval, a rejected file and expired authorization need different actions. Reconnection is not confirmation of publication. Read the duplicate prevention guide before resending content whose outcome remains uncertain. A successful connection step does not tell you what happened to an earlier upload.
5. Provide a useful diagnosis if it still fails
Include the network, visible account name, failing step and exact message, hiding sensitive details in screenshots. Explain whether other accounts work. This context is more helpful than repeatedly disconnecting everything and making the original issue harder to reconstruct. Keep the details focused on the account that actually needs attention.
A network refusal or outstanding external approval cannot be bypassed by repeating the connection. Relay aims to make these stages clearer; the public app is in preparation. Join the waitlist to discover an iPhone workflow that helps you resume publishing without turning every incident into a complete setup from scratch.
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 the network, account and workspace.
- Review source and destinations before changing anything.
- Start a new session with the correct identity.
- Verify outcomes without resending successful posts.
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.