Auto-Retry for Temporary Maintenance or 503 Errors

CheckView is built to ensure reliable, accurate testing, even when your site experiences short periods of downtime or maintenance. To prevent false failures during brief outages, CheckView includes automatic retry handling for test flows that encounter a temporary server issue on the initial page load.

When Auto-Retry Triggers

CheckView will automatically retry a test flow if, on the first page load of the first URL in the test sequence, it detects either of the following:

1. A 503 Service Unavailable status code returned by the server – This typically occurs when the server is under temporary load, restarting, or performing maintenance.
2. The default WordPress maintenance screen – This appears when WordPress is briefly updating plugins, themes, or core files, and displays a message such as “Briefly unavailable for scheduled maintenance. Check back in a minute.”

These are transient issues that usually resolve within seconds, so retrying avoids unnecessary false alerts.

How It Works

1. When CheckView begins a test flow, it attempts to load the first page of the test URL.
2. If a 503 status or WordPress maintenance message is detected, CheckView will wait 30 seconds and then the test will end with a failure. If the Auto-Retry setting is enabled in your organization settings, a new test run will automatically be created.
3. If the retry succeeds, the new test run is recorded as a separate passing test.
4. If the retry also fails with the same condition, the test will be marked as failed, and the result will include a note that a retry attempt was made.