Illustrator Save As Was Selectable During an Active Save but Then Rejected

Evaluations connected to this Case

These Evaluations explain how this experience contributes to a broader question. A connection may support, qualify, contextualize, or challenge a finding; open the Evaluation to read its evidence and limits.

• Illustrator “Document Is Currently Getting Saved” Blocks Save As
• Photoshop Makes You Wait to Start Save As While Another Save Finishes
• Illustrator Fixed a Blocking “Close While Saving” Dialog — Does the Reform Still Hold?
• Illustrator: A Later Save As Must Not Cancel the Save Already in Progress
• Illustrator Gets Stuck “Saving” and Blocks Save, Save As, and Save a Copy

Contributor objective

Save the working Illustrator document, then immediately prepare another copy under a different filename, location, or format without having to monitor the first Save and repeatedly retry Save As.

Observed sequence

1. The contributor initiated Save on an open Illustrator document.
2. While that Save was still active, the contributor selected File > Save As.
3. Illustrator displayed a modal saying the document was currently getting saved and to try again after the process completed.
4. The contributor dismissed the message and had to retry Save As until Illustrator became available.

Current finding

In this bounded occurrence, Save As remained selectable during an active Save but invocation did not preserve the user's requested next step. Illustrator instead returned a modal rejection and assigned the user the job of waiting, checking save state, reopening Save As, and retrying. The occurrence does not establish Adobe's internal technical reason or population prevalence.

Evidence and limits

Direct screenshot evidence establishes the exact active-save rejection message in this Illustrator occurrence. Contributor testimony establishes the action sequence, several-times-daily personal recurrence, and workflow burden. An independent Adobe-hosted Illustrator report describes materially similar Save As behavior and independently asks for the later Save As to wait for the current Save. Adobe documentation describes background saving as allowing continued work. These sources do not establish one mechanism across Illustrator versions or across Photoshop, Close, stalled-save, or save-cancellation scenarios.

Human impact

Friction

Save As is presented as selectable, but the user cannot complete or preserve the request. The user must dismiss a modal, remember the intended filename/location/format action, monitor when saving ends, reopen Save As, and try again.

Reported burden or pain

The contributor describes the interruption as especially frustrating because it occurs in a routine production workflow several times per day. The burden is not only elapsed save time; it repeatedly breaks concentration and transfers save-state monitoring back to the user.

Actual harm

In the documented occurrence, the user incurred a failed Save As attempt, modal dismissal, delay, and manual retry. The contributor reports this pattern recurs several times per day, creating a cumulative time and attention cost. No file corruption or data loss occurred in this bounded Incident.

Potential harm

Repeated failed Save As attempts can consume production time and attention and may cause a user to postpone or abandon an intended copy. Historical Illustrator reports show that unsafe sequencing of later save requests can create data-integrity risk, which is why HXR's requested reform requires safe serialization rather than concurrent writes.

Invisible taxes

Waiting, checking whether Illustrator is ready, reopening the menu, repeated command attempts, remembering the intended next save operation, and context switching away from the creative task.

Requested reform

While a valid background Save is active, let the user open Save As, choose the filename, location, and format, and preserve that request for safe execution after the current Save completes. Do not require repeated manual polling or retries. If Illustrator genuinely cannot accept Save As input during that state, make the command visibly unavailable before invocation and restore it automatically when safe rather than exposing an apparently available command that ends in a modal rejection.

Acceptance test

Start a normal Illustrator Save that remains active long enough to invoke Save As. If Save As is offered, one invocation lets the user enter the destination, filename, and format once; Illustrator preserves the request, completes the original Save without cancellation or corruption, and performs or resumes the pending Save As when safe. No repeated modal dismissal, menu reopening, or manual polling is required. If Save As cannot accept input safely, it is unavailable before invocation with understandable nonblocking status and automatically becomes available when safe.

What you can try now

Wait for the current Save to finish, dismiss the modal if it appears, and retry Save As. The contributor sometimes does another task while waiting, but that still requires the user to remember and manually retry the intended Save As operation.

Classification: Manual wait-and-retry / partial and burdensome

Organization response

No Adobe response to this HXR Incident has been requested or received. Adobe has publicly responded to related Illustrator Close-during-save and background-save cancellation reports, but HXR records those as separate related Evaluations rather than treating them as a response to this Save As occurrence.