Tracefox
Checkout monitoring report
Lumen Skincare (sample store)
- Period:
- Sep 15, 2026 to Oct 15, 2026
- Prepared:
- Oct 15, 12:00 PM UTC
64 checks of 4 checkout flows ran: 62 passed and 2 failed. The failed checks belong to 1 incident, which has recovered. 1 flow is paused.
- Checkout flows
- 4
- 3 on a schedule
- Checks run
- 64
- 62 passed, 2 failed
- Pass rate
- 96.9%
- of finished checks
- Incidents
- 1
- all recovered
What was checked
| Test | Viewport | Schedule | Checks | Pass rate | Last result |
|---|---|---|---|---|---|
| Add to cart and reach payment | Mobile | Daily | 30 | 93.3% | Passed, Oct 15, 6:00 AM UTC |
| WELCOME10 discount applies | Desktop | Daily | 30 | 100% | Passed, Oct 15, 7:00 AM UTC |
| Guest checkout reaches payment | Desktop | Weekly | 4 | 100% | Passed, Oct 9, 8:00 AM UTC |
| Shipping rates for Canada | Desktop | Paused | 0 | No runs | No checks |
Incidents
1 incident · 2 failed checks · recovered
An incident is a run of consecutive failed checks of one flow, until a check passes again. Times are when checks ran, not exact customer impact: a problem can start or end between checks.
The mobile check “Add to cart and reach payment” could not continue to shipping.
2 failed checks · recovered2 scheduled checks failed before the flow passed again.
- Flow
- Add to cart and reach payment (Mobile)
- First failed check
- Oct 9, 6:00 AM UTC
- Last failed check
- Oct 10, 6:00 AM UTC
- First passing check
- Oct 11, 6:00 AM UTC (2 days after the first failure)
- Failed checks
- 2 (2 scheduled)
- Evidence
- Screenshots of the failed check
Technical details
Step 9, “Continue to shipping” (click element)
Could not find the element to click. The selector "#continue-to-shipping" was not found on the page within the timeout. The page may have changed or the selector may be incorrect. Page state at failure: "#continue-to-shipping": 1 match but NONE visible (hidden duplicate, collapsed section, or display:none). Recorded: 0 fallback candidates.
Coverage
- Shipping rates for Canada is paused, so it is not checked on a schedule.
What this report covers
Each test checks the steps configured in it, on the viewport listed, in Chromium. Mobile and tablet are emulated screens, not real devices or Safari. These checks do not verify payment authorization. A test configured to complete a zero-total order can additionally verify order creation and confirmation. A failed check shows that a configured step could not be completed; it does not by itself show that customers were affected. Pages and steps that are not part of a test are not checked. Times are in UTC.
Technical appendix
The test runner's own messages, for whoever maintains the store. They describe what the test could not do, not necessarily why.
Add to cart and reach payment, Oct 9, 6:00 AM UTC, step 9 “Continue to shipping”
Could not find the element to click. The selector "#continue-to-shipping" was not found on the page within the timeout. The page may have changed or the selector may be incorrect. Page state at failure: "#continue-to-shipping": 1 match but NONE visible (hidden duplicate, collapsed section, or display:none). Recorded: 0 fallback candidates.