Check that people can still sign in
A login form posting to a broken session store still leaves the homepage returning 200. A flow monitor signs in, reads the token back, and calls the endpoint it authorises, so the sign-in itself is what gets checked.
- Sign-in checked each run
- JWT signature and expiry
- Failure names the step
Everything you need
A closer look at what you get, from the first check to the alert that reaches you.
Sign in the way your app does
Verify the token, not just the response
Then use it
A named failure, not a status code
Watch every sign-in run land
Each run signs in, checks the token and calls what it authorises; the first failing step is the one the alert names.
- Runs every 15 minutes at the fastest
- JWT signature and expiry checked
- Failure names the line
- Sign-in flowPassedRecovered · 4 steps in 1.2s
- Failed at step 4 of 4Failed
expect account.status 200 → got 401 - Sign-in flowPassed4 steps in 1.3s
- Sign-in flowPassed4 steps in 1.1s
- Sign-in flowPassed4 steps in 1.2s
How it works
Three steps from an empty dashboard to checks that run on their own.
Verify your domain
A flow drives a sequence against your host, so the team verifies it first.Write the sign-in
Post the fixture account's credentials, assert on the token, then call something it authorises.Get alerted on the failing step
A broken sign-in alerts through your existing channels, naming the assertion that failed.
Frequently asked questions
The questions people ask most before they start monitoring.
What credentials should a flow use?
A fixed fixture account. A flow replays the same spec every run and generates no data, so it can't invent a fresh signup address each time.
How quickly will I know the login broke?
A flow runs every 15 minutes at the fastest, hourly by default. Pair it with a 1-minute HTTP monitor on the endpoint the login depends on when you need faster detection.
Does this test the login page in a browser?
When you want it to. An HTTP login flow posts credentials and verifies the token. A browser login flow opens the page, fills the Email and Password fields, clicks Sign in, and asserts on the dashboard heading — catching failures that only appear after client-side code runs. Use whichever matches how the break would show up for a visitor.
Start monitoring your services
Create your first monitor in under 2 minutes. No credit card required to start.