Journeys: cart to checkout in a real browser
A shop being “up” says nothing about whether anyone can buy. A journey (journey) has a real browser (Chromium) load the start address every 15 minutes and work through a list of steps: click a product, add it to the cart, go to checkout, expect a text or an address. Step types: open page, click (selector or visible text), fill, select, expect text, expect URL (contains or pattern), expect status code, wait (at most 5 s). Templates for Shopware 6, WooCommerce and a login page are editable; a test run shows the outcome per step before you save.
If a step fails, the run is repeated after 45 seconds – only a second failure opens the critical incident journey_failed with step, error and the visible text of the page (browser runs flap because of layers, A/B tests and slow servers). If the run takes longer than the threshold (default 20 s), that is a warning (journey_slow). Values of form fields are stored encrypted and never appear in results or notifications. The browser identifies itself as “DomainWarn-Journey”; allow it in the shop’s bot protection or firewall if necessary. From the Agency plan (one journey per domain), Agency Pro three. In the dashboard, journeys have their own row in the “Website” tab of the domain; without a journey you start there from a template, with Shopware or WooCommerce detected right away from the matching one.