“Briefly Unavailable for Scheduled Maintenance”

Updates, Migrations & Maintenance

An update stopped halfway and left the closed sign hanging.

datacram.com/fix/briefly-unavailable-for-scheduled-maintenance
Likely causes, ranked
“Briefly Unavailable for Scheduled Maintenance”
An update timed outmost likely
Several updates run at oncecommon
The browser tab was closed mid-updatecommon
Memory exhausted during the updatepossible
Fix steps in this guide5
the causes explained below, most likely first
What you’re seeing

Every visitor sees a single line of plain text: “Briefly unavailable for scheduled maintenance. Check back in a minute.” The minute never ends, and the admin is unreachable too.

What it actually means

WordPress puts the site into maintenance mode during an update so nobody loads a half-updated page. It does this by writing a file called .maintenance in the site root, and it deletes that file the moment the update finishes.

If the update is interrupted — a timeout, a memory limit, a closed browser tab, two updates at once — the file is never deleted. WordPress finishes nothing, and the closed sign stays in the window indefinitely.

That makes this the most reassuring error on this whole site: the fix is deleting one file, and it takes about thirty seconds.

What usually causes it

Most likely first.

  1. 1

    An update timed out

    A large plugin or core update exceeded the execution limit and stopped partway through, leaving the flag file behind.

  2. 2

    Several updates run at once

    Bulk-updating many plugins together is the most common way to trip this, especially on modest hosting.

  3. 3

    The browser tab was closed mid-update

    Older WordPress versions relied on the request staying open. Closing it early stopped the process.

  4. 4

    Memory exhausted during the update

    The update process ran out of memory and was killed before its cleanup step.

  5. 5

    A file permission problem

    WordPress could write the .maintenance file but cannot delete it again.

How to fix it

Work through these in order. Take a backup before you change anything.

  1. Step 1Delete the .maintenance file

    Connect over SFTP or open the hosting file manager, look in the site root next to wp-config.php, and delete the file named .maintenance. It may be hidden — enable showing dotfiles. The site returns immediately.

  2. Step 2Check what state the update left behind

    Log in and look at Updates. The plugin or core update almost certainly did not finish, and a half-updated plugin can cause errors later.

  3. Step 3Re-run the update deliberately

    Update one item at a time rather than in bulk, and let each finish before starting the next.

  4. Step 4Raise limits before retrying

    If it times out again, increase the PHP memory limit and execution time. Those ceilings are usually what stopped it.

  5. Step 5Clear caches

    A page cache or CDN may still be serving the maintenance page after the file is gone. Purge both before assuming it did not work.

When to stop and call someone

Call someone if the site still fails after the file is deleted — that means the update left something genuinely broken rather than merely unfinished — or if you have no SFTP or file manager access, since there is no way to remove the file from the admin you cannot reach.

Frequently asked

Delete the file named .maintenance from your site's root directory using SFTP or your host's file manager. WordPress creates it when an update starts and removes it when the update finishes; if the update was interrupted, the file remains and the site stays closed until you delete it.

In the root of your WordPress installation, alongside wp-config.php and wp-load.php. It begins with a dot, so it may be hidden — enable showing hidden files in your SFTP client or file manager to see it.

No. It is a temporary flag with no content of value, and WordPress recreates it automatically the next time an update runs. Deleting it simply takes the site out of maintenance mode.

Usually a timeout or memory limit, most often when updating many plugins at once. The process is killed before it reaches its cleanup step. Updating one item at a time, with adequate memory and execution limits, prevents it recurring.

Then the update failed rather than merely stalled, leaving files half-replaced. Check the error log for a fatal error, and re-run the update deliberately. A half-updated plugin often needs reinstalling cleanly rather than updating again.

Free · AI-powered · Emailed to you

See exactly what’s holding your website back.

Get a free audit of your site — speed, SEO, mobile, and security — with the fixes that matter most, delivered as a PDF to your inbox.

Get my free audit
CallGet a quote