A page you asked SaaSMaestro to watch, such as pricing, signup or checkout, is broken. The rest of the website may look fine, so this can go unnoticed while it costs you sales.
What it means
The page didn’t load, answered with an error, or loaded without the text you said it must contain. That last case catches a page that answers “200 OK” but shows an error message or the wrong content.
What triggers it
Key page checks load each page every 5, 15 or 60 minutes, as you chose, and look for the text in the HTML as served, before any scripts run. After two failed checks in a row a Critical issue is raised with the page’s path and the reason, and owners and admins get a downtime email.
Common causes
- A deploy, plugin or theme update that broke the page.
- The page was moved, renamed or deleted, so it now returns 404.
- The page’s wording changed, so the expected text is no longer there.
- The text is added by JavaScript after the page loads, which the check can’t see.
How to fix it
- Open the page in a private browser window and compare what you see with the reason in the issue.
- If the page is broken, undo recent deploys or plugin updates, or ask your developer or host.
- If the wording or address changed on purpose, delete the check in the Key page checks dialog on Data connections and add it again with the new text or path.
When it clears
It clears at the first check the page loads and contains the text again, and whoever heard it was failing is told it works again.