Briefly unavailable for scheduled maintenance. Check back in a minute.
It is a polite message. The problem is that a minute has turned into an hour, the message is still there, and every visitor — and you — are locked out of the site, including the admin area.
This is one of the most common WordPress failures, and it almost always starts with something completely ordinary: an update.
What Maintenance Mode Is
Whenever WordPress updates its core, a plugin or a theme, it briefly takes the site offline so no visitor loads a half-replaced file. To do that it creates a small temporary file called .maintenance in the root of your installation. While that file exists, every request gets the "briefly unavailable" message.
When the update finishes, WordPress deletes the file and the site is back — normally within seconds. "Stuck in maintenance mode" simply means the update never reached its last step, so the file was never removed.
Why Updates Get Interrupted
The browser tab was closed too early
Updates started from the dashboard depend on the request finishing. Closing the tab, losing the connection or navigating away mid-update is the classic trigger.
Too many updates at once
Selecting twenty plugins and clicking "Update" queues them one after another. On slow or limited hosting, the process runs out of time or memory somewhere in the middle.
The server ran out of resources
Low PHP memory limits, short execution timeouts or a nearly full disk can stop an update halfway — sometimes after the old files were removed but before the new ones were fully written.
A plugin conflict or a failed download
If an update package is incomplete or incompatible with something else on the site, the process can die with a fatal error instead of finishing cleanly.
The Part Most Guides Skip
Search for this error and you will find the same advice everywhere: remove the leftover file and the message disappears. That is true — and it is also where many sites get into real trouble.
The maintenance message is not the problem. It is the sign that an update was cut off. Removing the sign does not finish the update. What you may be left with is a plugin that is half old and half new, a theme with missing files, or a database that was already migrated to a version the code no longer matches. The site comes back, looks fine for an hour, and then fails in a far less obvious way: a broken checkout, a white screen on one page type, an editor that no longer saves.
So the real questions are: which update was running, how far did it get, and is that component now complete and consistent? Answering them means checking the affected plugin or theme against a clean copy and reading the error log — not just making the message go away.
How to Avoid It Altogether
- Update in small batches, not everything in one click.
- Test updates on a staging copy first, so a failed update never happens on the live site.
- Take a backup immediately before updating — one you know can be restored.
- Check the site after every update, including forms, checkout and login, instead of assuming it worked.
- Make sure the hosting has enough headroom in memory, execution time and disk space.
None of this is complicated. It is just work that has to happen every single time — which is exactly why it gets skipped, and exactly why sites end up stuck on a Friday evening.