INVITATION-ONLY · PRIVATE-FIRST

7. Recover a failed upload without duplicates

The help pages are public. The app remains invitation-only. Public release and automatic client publishing are not enabled by these guides.

Reconcile the original job before retrying.

Step by step

Record the original publication ID, channel, language edition, status, and error. Check the native destination before trying again if the response was ambiguous.
For an expired or revoked channel grant, ask the owner to reconnect the same official channel inside the same workspace. Confirm the saved account before resuming.
Use the existing uploader’s retry/recovery control for the original failed publication when offered. Do not create a new upload or blindly rerun the whole bilingual workflow. If no safe retry control is available, contact the owner.
Watch the original record move through recovery. A spacing, concurrency, or daily-budget hold waits for admission; it is not permission to bypass the limit. A retry reuses its reservation.
After recovery, confirm one intended native video per edition and verify its private receipt. Keep the other already-successful edition intact.

What success looks like

The original publication recovers without an unintended second video. Both native destination state and the saved receipt agree.

Important limits

A 401/403 can require owner authorization; repeated clicking will not fix it. A timeout is an uncertain outcome, not proof that nothing uploaded. Never share refresh tokens or signed upload URLs.

Need more help?

Contact the workspace owner through your invitation or established support channel. Provide the page, approximate time, non-secret run/publication ID, and error text. Never share passwords, invitation links, OAuth tokens, signed media URLs, or private client content.

Troubleshooting guide