October 2026

The client called before the alert: 5 failures uptime checks miss

AgenciesJourneys

By Simon RaynaudFounder of Pathly · 3 min read ·

The site responds, uptime is green, and the client still calls. Here are five failures an availability check cannot see, and how to catch them first.

The worst call an agency can get: “My form hasn't worked since Monday.” Your monitoring stayed green the whole time. It was not wrong: the server was responding. It just was not looking in the right place.

1. The form loads but no longer sends

An update breaks submission, or the email service rejects messages. The page responds normally. Only a test that fills in the form, submits it and waits for the confirmation message will see it.

2. The Pay button stops responding

The payment provider's script changes, or a JavaScript conflict blocks the click. The cart loads, the order does not go through. Flow clicks the button and checks the page that follows.

3. A banner covers the main action

A cookie banner or a promotional pop-up covers the button on mobile. The content is there, but the visitor cannot click. The step screenshot shows it at a glance.

4. Logging in to the client area fails

An overly strict security plugin or a failing authentication service: the login page loads, but nobody can get in. A journey with a test account catches it.

5. The API behind the site stops keeping up

The site depends on an outside service: stock, bookings, shipping. That service answers slowly or returns an error, and the page stays up but empty. Chain chains the API calls the way the site makes them, and alerts when one of them breaks.

See the failure before the call

These five cases have one thing in common: you have to go through the journey to see them. Keep your availability check, and add a Flow on the journey that earns money. You get the alert with the screenshot, and you are the one who calls the client.

Why does uptime stay green?
Because it checks that the server responds, not that a visitor can finish. A page that loads with a broken button responds normally.
Should I replace my monitoring tool?
No. Keep it for availability, and add journey checks where an outage is costly.
How do I test a form without cluttering the client's inbox?
Use recognisable test content the client can filter, or a destination address reserved for tests if the form allows it.