Independent public-interest evaluations of how systems respect dignity and support agency.
HXR Evaluation
Illustrator “Document Is Currently Getting Saved” Blocks Save As
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.
- Evaluation ID
- HXR-EVAL-0027
- Status
- Open — gathering evidence
- HXR Incident connections
- 1
- Last updated
- August 25, 2026
Who and what this Evaluation covers
Naming an organization, product, service, or workflow identifies the subject of this Evaluation. It does not by itself prove which internal team caused or controls the issue.
- Organization in scope
- Adobe
- Product, service, or workflow
- Adobe Illustrator
Evaluation scope
Includes Adobe Illustrator desktop behavior for the same open document when a normal Save is actively progressing, File > Save As remains selectable, and the user invokes Save As before the current Save finishes. Includes command availability, Save As dialog access, preservation/queueing of filename/location/format intent, modal versus nonmodal feedback, manual retry burden, and safe deferred execution. Excludes stalled or indefinitely hung saves, Close-during-save behavior, cancellation of an active Save by later save requests, Photoshop implementation, generic background tasks, video rendering, all disk activity, operating-system multitasking generally, and claims about Adobe's hidden implementation unless separately supported.
Question being evaluated
When an Illustrator document is already saving in the background and Save As remains selectable, does Illustrator let the user specify and preserve the next Save As request until it can execute safely, or does it reject the request and require the user to dismiss a message and manually retry?
Current findings
What works well or deserves recognition
Illustrator supports background saving and allows continued work during the save. Adobe has also demonstrated in a related Close-during-save scenario that it can replace a blocking modal interaction with deferred/nonblocking behavior. Those facts are relevant feasibility and reform context but do not prove that Save As uses the same internal mechanism.
Difficulties and opportunities to improve
A valid active Save can leave Save As visibly/selectably available while invoking it produces a modal rejection. The user must dismiss the message, remember the intended next operation, monitor the application's save state, reopen Save As, and retry until the application accepts it. The burden is low per occurrence but contributor-reported as several times per day and therefore cumulatively meaningful. The interface currently assigns save-state polling and retry labor to the user instead of preserving the expressed next action.
Mixed findings and limits
The actual second file write may legitimately need to wait for the active Save to complete, and historical Illustrator reports show that unsafe sequencing can cancel an in-progress Save. HXR is therefore not asking for concurrent writes or bypassing data-integrity controls. The narrower question is whether Save As intent can be accepted and preserved while execution waits. If Adobe cannot safely accept Save As input during that state, disabling the command before invocation with clear nonmodal status is a weaker but more coherent alternative than presenting it and then rejecting it.
How HXR would test performance
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/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 disabled before invocation with understandable nonblocking status and automatically becomes available when safe.
Evidence coverage and limits
Contributor occurrence August 24, 2026; located Adobe-hosted reports and product documentation span 2019–2026. Coverage is evidence scope, not prevalence.
Connected HXR Incident reports
- Supports: HXR-2026-0824-0001 — Illustrator Save As Was Selectable During an Active Save but Then Rejected
1 public HXR Incident report is connected to this Evaluation. Canonical roles: 1 supports; 0 partially supports; 0 narrows; 0 context only; 0 challenges. Connections are not votes and do not establish prevalence.
Technical record details
- Evaluation type
- Interface
- Benchmark posture
- Developing Evidence
- Blue Score readiness
- Developmental Data Only
- Public revision
- 1