Product information

• Product: Adobe InDesign
• Primary affected version: InDesign 2026 21.4.1
• Other affected versions: [add versions tested]
• Operating system: macOS 27 beta [exact version/build]
• Platform: Apple silicon
• Severity: Critical / potential data loss
• Reproducibility: Frequent but intermittent

Report text

Problem description

InDesign repeatedly enters a save-locked state during ordinary editing on the macOS 27 beta.

After several successful saves, an open and modified .indd document suddenly can no longer be saved. The document tab continues to display the modified-document asterisk, but the following commands are disabled:

• Save
• Save As
• Save a Copy
• Revert

Closing the document is also unavailable or unsuccessful.

When quitting InDesign, the application reports:

InDesign cannot quit because one or more tasks are running in the background.

The Window → Utilities → Background Tasks panel is empty. There is no task to cancel, no progress indicator, and no visible alert explaining the failure.

Waiting does not restore saving. InDesign must eventually be force-quit, creating a substantial risk of losing work.

Expected behavior

A modified document should permit Save or Save As.

If a save or other background task is active, InDesign should:

• Show it in the Background Tasks panel.
• Complete it or return an actionable error.
• Re-enable document commands after completion or failure.
• Allow the user to cancel the operation where supported.
• Never remain permanently locked with unsaved changes and no recovery path.

Actual behavior

• InDesign recognizes the document as modified.
• All native save commands are disabled.
• The Background Tasks panel is empty.
• The application incorrectly claims that a background task prevents quitting.
• No recovery occurs.
• Force Quit is required.
• The only consistently successful rescue method has been IDML export followed by reopening and resaving the document.
• The failure later recurs.

Steps to reproduce

1. Run InDesign on macOS 27 beta.
2. Open an ordinary .indd file.
3. Make text or layout changes.
4. Save normally.
5. Continue editing and saving several times.
6. At an unpredictable point, make another edit.
7. Observe the asterisk in the document tab.
8. Open the File menu.
9. Observe that Save, Save As and Save a Copy are disabled.
10. Attempt to quit InDesign.
11. Observe the warning that background tasks are running.
12. Open the Background Tasks panel.
13. Observe that it is empty.

Frequency and scope

The failure occurs frequently and has been observed:

• In multiple documents.
• In multiple InDesign versions.
• With documents belonging to an .indb Book.
• With individual documents opened without relying on a cloud or network path.
• After IDML reconstruction.
• In relatively lightweight files.
• Without third-party plug-ins.

It may affect more than one open document during the same InDesign session.

Troubleshooting performed

The following have already been tested without resolving the issue:

• Deleted/reset InDesign preferences.
• Moved files to the local Desktop/internal SSD.
• Disabled Preflight.
• Confirmed the Background Tasks panel is empty.
• Exported files to IDML and recreated .indd files.
• Tested multiple InDesign files.
• Tested multiple InDesign versions.
• Confirmed no third-party plug-ins are installed.
• Confirmed the documents are relatively light.
• Tested outside cloud/network storage.

Book-file context

Several affected documents are components of an InDesign Book (.indb). However:

• The component files are independent native .indd files.
• The issue affects multiple files.
• Rebuilding the component documents through IDML does not permanently resolve it.
• The same behavior appears in more than one InDesign release.

The .indb context may be a trigger, particularly if numbering, synchronization or other book operations invoke an internal asynchronous task, but the visible Background Tasks queue remains empty.

Technical interpretation

The UI state suggests that InDesign internally believes a save or asynchronous operation is still active:

• The document dirty flag remains set.
• Save commands are disabled.
• Quit is blocked.
• No task is exposed in Background Tasks.
• No error is returned to the user.

This could involve:

• A leaked or unresolved background-task state.
• A save-operation flag that is never cleared.
• File coordination or atomic-save behavior under the macOS beta.
• An AppKit menu-validation incompatibility.
• A document/book synchronization callback that never completes.
• A macOS 27 compatibility regression affecting several InDesign releases.

Because it reproduces across InDesign versions on the same beta operating system, macOS is likely an important factor. Nevertheless, InDesign should fail safely and provide a recoverable error rather than disabling every save mechanism.

Production impact

This is a critical data-integrity problem.

Users may unknowingly continue working while the application is already incapable of saving. There is no warning when the failure state begins. The problem becomes visible only when the user attempts a save or quit.

Force Quit can discard all work since the last successful save. IDML export is only an emergency workaround and is not an acceptable replacement for reliable .indd saving.

System details

• InDesign: 21.4.1
• Additional versions tested: [versions]
• macOS: macOS 27 beta [version/build]
• Mac: [model]
• Processor: [processor]
• RAM: [RAM]
• Storage: Internal SSD
• Available disk space: [amount]
• Plug-ins: No third-party plug-ins
• Fonts used: Primarily Minion Pro and standard/Adobe fonts
• Documents: Text-heavy, relatively light .indd files; some managed through .indb

Attachments available

• Screenshot of disabled Save and Save As commands while the document is marked modified.
• Screenshot of the false background-task quit warning.
• Screenshot of the empty Background Tasks panel.
• Screenshot of the exact InDesign version.
• Sample .indd and .indb files, if Adobe requests them.
• macOS sysdiagnose and Adobe logs, if instructions are provided.
• Screen recording of the reproduction, if required.

Requested action

Please:

1. Reproduce the issue using InDesign 21.4.1 on the current macOS 27 beta.
2. Test both individual documents and documents included in an .indb.
3. Investigate save-state flags and hidden background operations.
4. Coordinate with Apple if the regression originates in macOS.
5. Provide a workaround that restores native saving without restarting or rebuilding through IDML.
6. Treat this as a high-priority data-loss issue.