Why it happens
Something in the release changed that step: a renamed field, a moved button, a new redirect, a permission that used to be there.
How to tell
- The journey fails at a named step, on every run, with a screenshot of the step.
- The publish that changed it, and its diff, when the repository is connected.
The fix
- Put the failing step's screenshot and the diff side by side; the cause is usually in the same component.
- Roll back, or fix forward.
- Run the journey again; recovery is confirmed when it passes.
The prompt for your builder
Paste this into Lovable, Bolt, Cursor, Claude Code or whatever built the app. Replace anything in capitals. It never asks you to paste a secret into a chat; keys go into your host’s environment, by you.
My checkout journey now fails at the step “STEP NAME” since the last publish. Compare the current component for that step with the previous version, explain what changed for a user at that point, and propose the smallest fix that restores the old behaviour.
How Keelnest catches it
Every publish re-runs the journeys within five minutes. The verdict says which step failed, with a screenshot, and what changed to cause it when the repository is connected. On Vercel and Netlify the same journeys run on the branch's preview before it is promoted, so the failed step is seen while the fix is still a branch.
Know the moment this happens.
Keelnest watches your production app every five minutes and tells you in plain English what broke — with the fix. Free for your first app.
Related
- Errors spike right after a publishWithin minutes of a deploy, error capture shows dozens of the same error on one page.The fix
- Sign-in breaks on your new domainYou moved to a custom domain. Existing sessions still work; new sign-ins fail after the magic link or the OAuth redirect, with “redirect_to is not allowed”.The fix