Distinguish an active update from a stale marker
Confirm the WordPress update has stopped before removing a stale maintenance marker, then complete and verify the update.
WordPress uses a temporary maintenance marker while an update is running. If the message remains after the update should have completed, first ask the site administrator whether another person or automation is still updating core, a plugin or a theme. Note when the message began and whether the admin area is also unavailable. Do not remove the marker while a real update is active: visitors could reach a partially changed application.
This guide is for the WordPress message “Briefly unavailable for scheduled maintenance”, not an unrelated hosting 503 page. Confirm the exact installed application and domain, and keep a backup of the current files and database before completing an interrupted update. A failed update can leave code and database versions out of step.
Find the marker in the exact WordPress base directory
If the update is no longer running and the application owner has an authorised file manager or transfer account, open the actual WordPress base directory: the directory containing wp-admin. WordPress documents a hidden .maintenance file there. Enable display of hidden files if the account tool requires it. Check the directory path and marker time against the interrupted update. An account can have several domains or WordPress installations, so do not delete a similarly named file elsewhere.
Retain a private copy or at least the timestamp and path for the incident record, then remove only that stale .maintenance file. Do not remove wp-content, update archives or a server-level maintenance configuration. If the entitled account cannot see the file, ask the application owner or support to confirm the correct account path rather than changing global permissions.
Complete the interrupted application update
Refresh the public page and sign in to WordPress. The missing maintenance message only shows that the marker is gone; it does not show that the update succeeded. Inspect the dashboard Updates screen for an incomplete or failed core, plugin or theme update. Follow WordPress’s supported update or manual recovery instructions for the exact component, using the known-good backup if needed. Avoid clicking Update repeatedly while the cause is unknown.
Check operation and stop a recurring failure
Test the home page, one inner page and the admin area in a fresh session. Confirm the expected application and component versions and a representative feature. If .maintenance reappears because a retry fails, stop deleting it repeatedly. Record the error, time and component for the application owner; ask platform support about a demonstrated account-level write or resource fault. Keep the backup available until the completed update is verified.
For example, once no update is running, remove only the confirmed stale marker. Verify a public page and the update status; a working home page can hide an incomplete plugin update.
Frequently asked questions
Can I delete the marker immediately? First confirm no update is still running. The file is part of the normal update process.
Does removing it repair a failed update? No. It removes the message; the interrupted update still needs checking and possibly completion or rollback.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.