Auto‑Save Fails Silently When Network Share Disconnects During After Effects CC 2020 Upgrade

Short answer

After Effects CC 2020 (v17.x) has no documented mechanism to detect, report, or recover from a failed Auto‑Save when the target folder becomes unavailable mid‑session. If the Auto‑Save location is a network share that drops, you should assume the save is skipped without any user‑visible alert, and the Version History panel will contain no entry for that interval. There is no documented preference or environment variable that forces a fallback to a local folder or pops up a warning.

What is well established vs. what is uncertain

It is important to separate confirmed behavior from assumptions, because some commonly repeated claims about this setup are not documented by Adobe:

• Documented: The Auto‑Save location is configured in After Effects via Edit → Preferences → Auto‑Save (Windows) or After Effects → Preferences → Auto‑Save (macOS), where you can choose a custom folder and set the interval and maximum number of versions.
• Not documented: An AE_AUTOSAVE_PATH environment variable. There is no official Adobe documentation that After Effects reads this variable, so workflows built on it should be treated as unverified. If your team relies on it, verify on your exact build before trusting it.
• Not documented: An AE_ENABLE_LOGGING variable or a dedicated Auto‑Save failure log with specific message strings. After Effects does write general diagnostic logs, but a guaranteed, greppable record of a skipped Auto‑Save is not a documented feature.

Why the failure is silent

Auto‑Save in After Effects is a background convenience, not a transactional save. The application does not treat a failed Auto‑Save as an error condition worth interrupting the user over, and the Version History panel only lists versions that were actually written. A skipped write therefore leaves no trace in the UI, and on the next launch there is no recovery project because no file was created. This matches the symptom described; the precise internal reason (whether the write is attempted and discarded, or skipped after a path check) is not publicly documented.

Practical steps for this case

1. Stop relying on the network share. Point Preferences → Auto‑Save at a local folder and let a sync tool (or scheduled copy) mirror versions to the share when it is available.
2. Verify share availability before launch. If you must keep Auto‑Save on a share, gate the launch with a small wrapper check, e.g. on Windows: if exist \\SERVER\Share\ (start ae) else (echo share offline). This is external to After Effects because the application itself offers no fallback.
3. Confirm behavior on your exact build. Disconnect the share during a session, wait past the Auto‑Save interval, and check whether the Version History panel gained an entry and whether any file appeared. Do not assume a fallback occurred.

One open question

If you are seeing an upgrade specifically reset or ignore your Auto‑Save folder setting, the missing detail is whether the share was unreachable at launch or only mid‑session — the former can plausibly cause the preference to be re‑validated, while the latter is the silent‑skip case above. That distinction changes whether the fix is a pre‑launch check or a local‑folder workflow.