Introduction

When WordPress auto-save stops working, editors usually notice it only after losing a paragraph, a draft change, or a full editing session. The failure is rarely random. It usually traces back to blocked REST requests, expired sessions, JavaScript errors, or plugins that interfere with the editor heartbeat. The quickest fix is to inspect what happens in the editor network flow at the moment an auto-save should fire.

Symptoms

  • Draft changes are not saved automatically while editing posts or pages
  • The editor shows update failures or stale content warnings
  • Revisions stop appearing even after several minutes of editing
  • The problem affects the block editor more than the front end
  • Auto-save broke after a plugin, security, or caching change

Common Causes

  • REST API requests used by the editor are failing or blocked
  • The Heartbeat API is disabled, throttled too hard, or interrupted
  • Session or nonce expiration causes background save requests to be rejected
  • JavaScript errors in the admin area stop the editor workflow before auto-save runs
  • Security, CDN, or firewall rules interfere with admin POST requests

Step-by-Step Fix

  1. Open the browser developer tools while editing a draft and watch the network and console activity when auto-save should occur.
  2. Check whether REST API or admin-ajax requests are failing with 401, 403, 400, or timeout responses.
  3. Confirm the user session is still valid and that the editor is not working with an expired nonce or logged-out state.
  4. Review plugins or performance settings that disable or aggressively throttle the Heartbeat API.
  5. Inspect JavaScript console errors in wp-admin and temporarily disable the most recent editor-related plugin if errors appeared after an update.
  6. Bypass page caching, security middleware, or proxy rules that should never affect authenticated admin save requests.
  7. Re-test with a default theme and minimal plugin set if the failure is still unclear.
  8. Confirm that revisions and draft timestamps now update automatically during a normal editing session.
  9. Keep admin-side optimization rules conservative so background editor workflows are not treated like disposable traffic.