Independent public-interest evaluations of how systems respect dignity and support agency.
HXR Evaluation
Illustrator: A Later Save As Must Not Cancel the Save Already in Progress
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.
- Evaluation ID
- HXR-EVAL-0030
- Status
- Monitoring
- 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 Illustrator reports where a later Save As or related save request interacts with an already active background Save and risks cancellation, stale saved state, or loss of the first write. Excludes mere modal rejection with a normally completing Save, Close behavior, indefinite/stalled saves, Photoshop, and generic concurrency architecture.
Question being evaluated
When another Save As or save-related request is issued while an Illustrator Save is already in progress, does Illustrator preserve the active Save and serialize later work without canceling, superseding, or corrupting the file already being written?
Current findings
What works well or deserves recognition
Adobe reported fixing a related background-save cancellation bug in a later Illustrator release. The existence of that fix and user queueing proposals support a design direction in which later save requests are serialized rather than allowed to invalidate an active write.
Difficulties and opportunities to improve
Historical reports describe later save operations canceling or aborting an active Save without a sufficiently clear user expectation, creating stale-file and work-loss risk.
Mixed findings and limits
The located historical reports may involve version-specific or scripting contexts and do not establish current recurrence. They are nevertheless material safety evidence for any Save As queue/deferred-execution reform.
How HXR would test performance
While an Illustrator Save is actively writing, issue a subsequent Save As/save request. The original Save completes successfully and remains intact; later work waits or is serialized safely; the user receives clear state feedback; no active write is silently canceled, replaced, or left stale. Repeating the test across supported storage contexts does not produce data loss.
Evidence coverage and limits
Historical Illustrator UserVoice reports and Adobe fix response reviewed August 24, 2026.
Connected HXR Incident reports
- Context Only: 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: 0 supports; 0 partially supports; 0 narrows; 1 context only; 0 challenges. Connections are not votes and do not establish prevalence.
Technical record details
- Evaluation type
- Mechanism
- Benchmark posture
- Developing Evidence
- Blue Score readiness
- Developmental Data Only
- Public revision
- 1