Adobe Illustrator Evaluations and Incident reports

Save As can remain selectable during a background save, then reject the request instead of preserving the filename, location, and format for when the current save finishes. Direct contributor evidence from August 24, 2026 shows Illustrator displaying that the document is currently getting saved and to try again after the process is complete after Save As was invoked during an active save. The contributor reports this occurs several times per day in ordinary production work. Independent Adobe-hosted UserVoice material describes the same Save As condition and asks for Save As to begin after the current save completes, as in previous versions. Adobe documentation says Illustrator saves .ai files in the background so users can continue working, but the located documentation does not explain why a selectable Save As command must reject the request instead of collecting the user's choices for later execution. The current evidence supports a recurring workflow problem and concrete reform target; it does not establish population prevalence, Adobe motive, or the exact internal mechanism.

Adobe changed a related while-saving workflow so Close could be preserved while the save finished; HXR tracks that reform separately from Save As and stalled-save behavior. Adobe Illustrator UserVoice records a widely supported complaint that Command-S followed by Command-W produced a blocking dialog requiring an extra OK before the document would close. Adobe Illustrator team staff responded that the dialog was removed in Illustrator 24.1/24.1.1 and replaced with a new experience. Later comments reported edge cases, but the record demonstrates a concrete Adobe reform of a closely related while-saving interaction. This Evaluation is kept separate from Save As because the user objective and implementation path may differ.

Any improvement to Save As during background saving has to preserve the original Save first; historical reports show why safe sequencing matters. Adobe Illustrator UserVoice reports describe cases in which a subsequent Save As or save-related action interrupted or canceled the Save already in progress, creating risk that the main Illustrator file remained outdated while another output contained newer work. A related UserVoice thread includes a user proposal to queue later save operations and an Adobe-team statement that a background-save cancellation bug was fixed in a later release. This is a distinct safety/data-integrity Evaluation: the main Save As workflow reform is acceptable only if it preserves the first Save.

Recent users report a persistent saving state that can last far beyond a normal save and leave force quit or file reconstruction as the only apparent escape. Recent Adobe Community reports around Illustrator 29.7.1 and later describe documents remaining stuck in a saving state, with Save, Save As, and Save a Copy blocked and some users forced to quit, recover, copy work to new files, or use alternate export paths. Adobe Community Managers asked for version/storage details and stated that the product team attempted a fix in an Illustrator beta. The visible error text can match the ordinary Save As rejection seen in the main Incident, but the duration, recovery path, and likely failure mechanism are materially different, so HXR keeps this as a separate related Evaluation.