Illustrator “Document Is Currently Getting Saved” Blocks Save As

August 25, 2026 Human Experience Reform

Human Experience Reform public Evaluation

Stable Evaluation ID: HXR-EVAL-0027

Adobe Illustrator: Save As Request Handling During an Active Background Save

A selectable command should not become a modal “try again later” trap when the application could preserve the user's next action.

Bounded Evaluation: this is about Save As on the same Illustrator document during a normally progressing Save. Stalled saves, Close, Photoshop, and active-save cancellation are tracked separately.

In plain English

Direct evidence shows Illustrator displaying “The document is currently getting saved. Try again after the process is complete.” after the user invoked Save As during an active background save. The contributor reports this happens several times per day in production work.

Why this matters

The user has already expressed a valid next step: save another version under a different name, location, or format. Rejecting the request forces modal dismissal, save-state monitoring, memory of the intended operation, menu reopening, and repeated retry.

Evidence and limits

Supported

Direct screenshot of the active-save rejection.
Contributor-reported several-times-daily recurrence.
An independent Adobe-hosted report describing materially similar behavior.
Adobe documentation describing background saving as continued-work support.

Not established

Population prevalence or every Illustrator version.
Adobe's internal technical constraint or motive.
That concurrent file writes are safe or required.
Data loss in this bounded occurrence.

Current findings

Positive: Illustrator already supports background saving and Adobe has used deferred/nonblocking handling in a related Close-during-save workflow.

Negative: Save As can remain visibly available, then reject the user's request and transfer polling and retry work back to the user.

Safety boundary: HXR is not asking Illustrator to write two files concurrently or bypass data-integrity controls. Safe deferred execution satisfies the objective.

Reform requested

If Save As is offered, let the user enter destination, filename, and format once, preserve the request, finish the original Save safely, and resume the pending Save As when safe. If Illustrator cannot accept the request safely, disable the command before invocation with understandable nonblocking status and restore it automatically.

Acceptance test

Start a normal Illustrator Save that remains active long enough to invoke Save As. If Save As is offered, one invocation captures the user's choices, preserves the first Save without cancellation or corruption, and performs or resumes the later operation safely. No repeated modal dismissal, menu reopening, or manual polling is required.

What could change HXR's view?

Current-version tests across operating systems and storage targets.
An Adobe explanation of the safety or architecture constraints.
Evidence that Save As is now queued, deferred, or coherently disabled.
Regression tests showing the first Save remains intact.

Adobe: respond or document reform

An authorized representative may correct facts, explain constraints, provide current behavior or QA evidence, propose reform, document implementation, or request verification.

Start a private organization response

Have you encountered this?

Useful context includes Illustrator version, operating system, storage location, whether Save As was selectable, exact message, whether the first Save completed, and whether retrying later worked. Do not expose private file names or customer artwork.

Back to blog