Resolve subtitle saving problems
Identify pending, failed or uncertain saves, keep unsaved text safe, and resolve conflicts without overwriting another writer.
Before you start
Keep the affected editor tab open. Both account and guest edits need a working connection to the server. A saved status means acknowledged subtitle content, not a write into the original media. Copy important unsaved text and its cue times somewhere safe before reloading.
Retry the save or resolve the conflict
Read the save state
Read the status beside Export. Is saving pending, did it fail, or is acknowledgement uncertain? A changed or removed document needs a different response. Keep this tab open while checking.
Retry the existing save
Restore the connection, then use Retry if offered. Wait for Saved. Retry checks the existing save attempt; it does not grant permission to overwrite another tab’s changes.
Resolve a conflict after preserving local work
Copy unsaved text and times somewhere safe before choosing Reload. Inspect the current stored document, then reapply your changes. If the asset was removed or is unavailable, retrying cannot recreate it.
Result
The saved state acknowledges the intended document, or your unsaved work remains separately preserved while the conflict is unresolved.
Check the result
Reopen the same asset after a confirmed save and check the changed cue. Export only after acknowledgement. A physical-source reconnect is unrelated to a conflict in already stored subtitle text.
If something goes wrong
If storage or connection remains unavailable, keep the tab and preserve the text; do not clear browser data as a repair. For account-access problems use Security or support. Export recovery covers destination failures after a successful save.