Illustrator: A Later Save As Must Not Cancel the Save Already in Progress

Human Experience Reform

Human Experience Reform safety Evaluation

Stable Evaluation ID: HXR-EVAL-0030

Illustrator Active-Save Preservation When a Later Save Request Occurs

A follow-on Save As must never silently sacrifice the Save the user already trusted Illustrator to complete.

Distinct scope: this Evaluation protects the active Save itself. HXR-EVAL-0027 separately evaluates whether the later Save As intent is preserved without repeated retry.

In plain English

Historical Adobe-hosted Illustrator reports describe cases in which asking for another save operation while a background Save was running could cancel or supersede the original Save. Adobe staff later reported changes intended to preserve the first save. This record keeps the data-integrity invariant explicit and monitors whether the reform remains true.

Why this matters

The first Save represents an explicit user decision to protect current work. A later request may wait, queue, or fail safely, but it must not retroactively cancel the confirmed operation or leave the user believing work was saved when it was not.

Current findings

Historical negative: Adobe-hosted reports documented active-save cancellation or loss under later save interactions.

Positive reform evidence: Adobe staff acknowledged the problem and described a fix in later Illustrator versions.

Limit: historical implementation evidence does not prove every current version, storage condition, or later save pathway remains safe. This is a durable invariant requiring regression testing.

Reform and preservation requirement

Guarantee that once a Save is accepted, its write either completes or ends in a clear recoverable failure state. Later Save, Save As, Save a Copy, Close, or export requests may be serialized, queued, or rejected coherently, but must not silently cancel, supersede, or corrupt the active Save.

Acceptance test

Start an Illustrator background Save, then invoke a later save-related action under supported conditions. The original Save completes with verifiable file integrity or displays a clear recoverable failure. The later request is safely deferred, queued, or rejected without canceling or silently replacing the first Save. Reopen the original file and verify the expected content and timestamp.

What could change HXR's view?

  • Current regression-test evidence across supported OS and storage targets.
  • Adobe implementation details proving the active-save invariant.
  • A reproducible current cancellation or corruption regression.
  • Evidence that related actions now share safe serialization controls.

Adobe: confirm or challenge the invariant

An authorized representative may document current safeguards, identify fixed or affected versions, correct the historical interpretation, report a regression, or request verification.

Start a private organization response

Have you encountered this?

Describe Illustrator version, OS, storage type, first Save action, later command, visible status, whether the original file updated, and what happened after reopening. Do not upload private artwork or customer files publicly.

Back to blog

Leave a comment

No account or purchase needed. Add your name, email, and comment below.

Your name and comment will be public once published. Your email address will not be displayed.

Comments are reviewed before appearing here, so yours will not show immediately.