Key takeaway

Protect your current changes before troubleshooting a save failure. Saving on this device and cloud sync are separate operations; losing network access does not necessarily prevent a local save. This guide applies to clients that provide save failure details. Open How to fix this in the failure details, or search for save failed in Help.

Protect your unsaved changes first

1. Stay in the editor for now. Open the failure details and choose Copy text.
2. Paste the text into a local app or file you trust. Reopen it and check the beginning, end and important paragraphs. Copying is not the same as saving the script.
3. Plain text does not back up bold text, colors, the outline, cue identities or hotword settings. Record those settings separately if you need them.
4. Do not clear this app's data, uninstall it or force stop it. The operating system may terminate a background process; text remaining in the editor is not proof that it was stored.
5. If copying also fails, preserve important passages in smaller parts or take screenshots, and mention the copying failure in your feedback. Do not experiment by deleting app data.

Device storage is full

1. Protect your text first, then search for Storage in your phone settings and check the available space.
2. Remove only downloads or media you have backed up and no longer need. Do not delete this app's data, script database or model files.
3. Return to the original editor, choose Retry or Save, and wait for an explicit saved status.
4. Return to the script list and reopen the script to check the latest text. A disappearing error is not proof of success.
5. If this message persists while the phone reports free space, the local database may have a separate writable capacity limit. Keep your text and send feedback; do not repeatedly clear data or reinstall.

Local data could not be written

1. Protect your text, wait briefly, then retry once in the original editor and check its save status.
2. Check whether other apps or the system report storage or file errors. Stop any cleanup operation affecting this app's files.
3. If saving still fails, record the time and steps and use Send feedback. Signing in again, changing media permissions or reinstalling is not a general fix for private local script storage.
4. Before restarting the phone, confirm that your text has been preserved. Restarting ends the current unsaved editing session and does not guarantee draft recovery.

The local database is busy

1. Your current text is still in the editor. Protect important passages and wait briefly.
2. Let current script or sync operations finish, then tap Retry once. Do not tap Save rapidly and repeatedly.
3. Reopen the script after success to check it. If the error continues, report the time and whether you had just imported, synced or switched pages.
4. Do not clear app data to release a lock, or force stop the app before protecting unsaved text.

The script database has a problem

1. Immediately preserve the visible text. Back up other important scripts that can still be opened if needed.
2. Do not clear app data, uninstall, downgrade, or manually change or delete database files. These actions may lose existing scripts.
3. Report the failing step, whether other scripts open, and any recent unexpected shutdown or cleanup operation. Include diagnostic logs if you choose.
4. This error normally requires developer investigation. Freeing space or repeatedly retrying cannot guarantee a repair. Keep your backups until a specific recovery plan is available.

The script could not be written

1. Protect your text. A rejected complete save is not proof that the body, hotwords or scan state were partially saved.
2. Retry once in the original editor. After success, reopen the script and check the latest content.
3. If it still fails, report recent imports, cue, outline, hotword or sync changes. This helps locate validation and complete-write problems.
4. Do not erase all cues, headings or hotwords to bypass the error, and do not clear app data.

Local storage is unavailable

1. This message does not identify a specific capacity, file or database cause. Protect your text first.
2. Retry once later in the original editor. Check the saved status and reopen the script to verify the content.
3. If it still fails, note the time and exact details and send diagnostics through feedback. Do not delete app data simply because the message mentions storage.

The script or account has changed

• Edited elsewhere: preserve the current text. Reopening discards unsaved changes; confirm first, then reopen and manually merge the text you need.
• Account changed: do not repeatedly switch accounts or write the draft into another account. Preserve the text, confirm the current account and follow the page instructions. Report persistent failures.
• Script missing: preserve the text and check the script list or recycle bin. Creating a script with the same title does not restore the original script.

Check limits and input

• Script limit: Free supports up to five active scripts you create. Delete only a backed-up script you no longer need, or upgrade if appropriate.
• Text limit: use the actual count and limit in the current error details. Free supports 5,000 characters and Pro 100,000. Spaces, punctuation and cue text count too. Preserve the original, then shorten or split it; the app does not silently truncate it for you.
• Expired membership: being able to open a long script does not mean it can still be written under Pro limits. A title-only edit checks the whole body too.
• Invalid title: check the title field and follow the prompt, then retry. Preserve the draft before changing it.

AI Follow terms need fixing

1. Protect your current text first. Return to the editor, expand AI Follow terms, and read the red field errors.
2. Each entry needs a body term and at least one accepted pronunciation. Pronunciation 2 is optional. If you do not need a newly added empty entry, delete that entry; you do not need to clear all terms.
3. The body term must appear in readable text, not only in a static cue. Check spelling, spaces and punctuation, and review the term after changing the body.
4. Follow the field errors to fix duplicate terms, duplicate pronunciations, and pronunciation conflicts between entries. One pronunciation cannot point to two different body terms.
5. After fixing the entries, tap Retry or Save in the original editor. Confirm that saving completes, then reopen and check the body and terms. Copying the body does not back up the term settings.
6. If saving still fails, record the exact prompt and recent term changes and use Report a problem with diagnostics. Do not clear app data or uninstall to investigate.

Script structure or scan state errors

If the outline, cues or scan state are invalid, preserve the text and note recent related edits. Retry once, then report persistent failures instead of clearing all structure data. A scan-state update failure means the complete script save did not finish; an old scan result is not proof that it matches the new body.

The cause is unclear or saving still fails

1. Open Send feedback from the save details, or Me → Feedback. Existing form drafts are kept; check that the related feature is Script editing.
2. State the time, error details and whether this was a new script, update or copy. Mention recent imports, cue or hotword edits, sync and account switches.
3. Choose screenshots or diagnostics if useful. After generating the feedback package, online submission requires sign-in and your explicit action; you can also choose another sharing method. Opening Help or Feedback does not submit anything automatically.
4. Do not paste passwords, verification codes or the full private body into the description. You keep your text backup; opening this guide does not attach it to feedback.