Sample run. The store and the failure are made up, and the screenshots are of a test storefront we built for this page. The layout is the run page you get in the app.
Add to cart and reach payment
Lumen Skincare (sample store)
- Trigger
- Scheduled, daily
- Viewport
- Mobile (375 by 812, emulated in Chromium)
- Stops at
- Payment section appears, before paying
- Started
- Oct 9, 2026, 6:00 AM UTC
The test could not get to shipping: the “Continue to shipping” button was on the page but never became visible. It was re-run once to rule out a blip, failed the same way, and an alert was sent. Show the error and screenshot
This was the first of two failed scheduled checks; the next day's check failed the same way, and the flow passed again on Oct 11. The sample client report shows it as one incident.
Select size 50 ml
Add to cart
Cart shows 1 item
Checkout
Address
City
Postal code
Continue to shipping
Shipping methods are listed
Continue to payment
Payment section appears
What this run does and does not show
- It shows the steps configured in this test, on one emulated mobile viewport, in Chromium.
- It does not show whether Safari or a real phone behaves the same way.
- It stops before payment, so it says nothing about whether a payment would be authorized. Steps after the failure were skipped.
- It records what the test saw, not why: a hidden button can come from a theme change, an app, or a stock or region rule.