Briefly Unavailable for Scheduled Maintenance? What to Do

Your website is showing “Briefly unavailable for scheduled maintenance. Check back in a minute.” That means WordPress put the site into maintenance mode while it installs an update. WordPress’s own documentation opens with “don’t panic” and says someone has likely seen the same message before and that it can easily be solved.

While that notice is up, visitors see it instead of your pages, your contact form or your checkout. The calls, bookings and sales that come through the site wait until it clears. Here’s the plan. Wait a minute and reload. If the notice stays, remove the one leftover file WordPress’s documentation names. Then check that the update finished.

What Does “Briefly Unavailable for Scheduled Maintenance” Mean?

WordPress installs a .maintenance file on its own when it updates. That file is what shows the notice while the update runs. According to WordPress’s guide to common errors, you may see “Briefly unavailable for scheduled maintenance” after an upgrade because that file may not have been removed properly.

That’s what people mean by WordPress maintenance mode. It can start on its own. WordPress’s updating guide says sites can apply minor and security updates automatically in the background, so the notice can appear when nobody clicked an update button.

Should You Wait or Fix It?

Wait a minute, then reload. The message asks visitors to check back in a minute, so give the update that long before you touch anything. Let it run. These steps keep you from cutting into an update that hasn’t finished.

• If you or someone on your team started an update in the dashboard, let that screen finish before you do anything else.
• Don’t start another update while the notice is up.
• Reload the site after a few minutes.
• If the notice is still there, the update has finished or stopped and left the file behind. Removing that file is the fix.

If you saw this message on someone else’s website, there’s nothing to fix on your side, so try again later.

How Do You Remove the Leftover Maintenance File?

WordPress’s documented fix is to delete one file. You open the website’s files, go to the site root and delete the file named .maintenance. The site root is the main folder where WordPress is installed. WordPress’s error documentation says to reach those files with an FTP program, a tool that connects your computer to your website’s folders.

• Connect to the website’s files with an FTP program, or open your host’s file manager if your hosting account has one.
• Open the site root.
• Find the file named .maintenance and delete it.
• Reload the website.

One tip for this step: the file’s name starts with a dot, and some file tools hide files like that until you choose to show hidden files.

The same fix appears in WordPress’s guide to updating: when a “failed update” message shows up, delete the .maintenance file. Deleting it clears the notice for visitors. It doesn’t finish the update, though, and that part is worth checking.

What If You Don’t Use an FTP Program?

Some hosting accounts include a file manager that opens the same folders. WordPress’s documentation names the FTP route, and a file manager reaches the same place. Either way, you’re after one file in the site root. If neither is open to you, hand this to whoever looks after the site.

What Should You Check Once the Site Is Back?

Check that the update finished. WordPress’s documentation says an automatic update can fail from a glitch in the connection with WordPress’s files, a problem with the internet connection during the update, or incorrect file permissions. Deleting the leftover file clears the notice, so the update itself still needs a look.

• Open the dashboard’s updates screen and see whether the plugin, theme or WordPress update still shows as waiting.
• If it does, run it again and let it finish.
• Open your main pages and read them as a visitor would.
• Open your contact or booking form, and your checkout if you have one.
• If the same update stalls a second time, that’s the point to hand it over.

If a different message shows up instead, such as WordPress’s critical error notice, Spilt Media’s post on what a WordPress critical error means walks through that one.

How Do You Keep It From Happening Again?

Back up the website before you update it. WordPress’s updating guide says that’s a good idea, because a backup means you can restore the site if there are issues. The rest is habit: update in small steps, and give each one time to finish.

• Keep a current backup before any update.
• Update one plugin or theme at a time, and let each one finish.
• Run updates when the site is quiet, so fewer visitors meet the notice if it sticks.
• Try updates away from the live site first, so a stalled one doesn’t reach visitors.

Spilt Media’s post on how to plan WordPress updates with a rollback covers that backup-and-test routine in more depth.

When Is It Worth Handing It Off?

Hand it off when the files aren’t your job. That’s the call when you don’t have FTP or file manager access, when you’re not sure which folder is the site root, when the notice comes back after updates, or when something else breaks once it clears.

Spilt Media’s WordPress support plans test every WordPress core, plugin and theme update in a staging environment before it reaches the live site, and keep daily backups with one-click restoration.

Those plans also monitor uptime around the clock.

Want updates and backups off your plate? You can book a consultation with Spilt Media to talk through how updates and backups are handled on your site.

Frequently Asked Questions About WordPress Maintenance Mode

What is WordPress maintenance mode?

It’s the state WordPress puts your site in while it installs an update. WordPress installs a .maintenance file, and that file is what shows visitors the short maintenance notice. Once the file is gone, the notice clears.

How long should the maintenance message last?

The message asks visitors to check back in a minute, so give it that long. Reload after a few minutes. If it’s still up, look for the leftover .maintenance file in your site root and delete it. That one file is what holds the notice in place.

Is it safe to delete the .maintenance file?

WordPress’s documentation gives deleting that file as the fix for the stuck message. Removing it clears the notice for visitors. It doesn’t finish the update, though. Open your dashboard’s updates screen afterwards, and run the update again if it still shows as waiting.

Why did my site go into maintenance mode when nobody updated anything?

WordPress’s updating guide says sites can apply minor and security updates automatically in the background. So maintenance mode can start without anyone clicking a button in the dashboard. If the notice stays after one of those background updates, the leftover file is holding it up. Deleting it clears the notice.