The weekly production form check failed: https://github.com/scanopy/website/actions/runs/29239952986
A lead-capture form on scanopy.net may be silently broken — a prospect
filling it out could be getting no response. Treat as revenue-impacting.
The Playwright report (screenshots + traces) is attached to the run as an artifact.
Failure messages decode as follows:
FORM DID NOT SUBMIT — clicking submit fired no request to Brevo.
Broken page JS or unwired handler (the June 2026 failure mode).BREVO HTTP ERROR <status> — the request fired but Brevo returned an error.
Check whether the Brevo form still exists / the endpoint URL changed.BREVO RESPONSE NOT JSON — endpoint is not behaving like a Brevo form
(redirect, HTML error page, moved URL).BREVO REJECTED SUBMISSION — 2xx but success:false; body included in the message.- A success-UI assertion failure — Brevo accepted the data but the user-visible
confirmation never appeared.
See the "Form Monitoring" section of the README.
The weekly production form check failed: https://github.com/scanopy/website/actions/runs/29239952986
A lead-capture form on scanopy.net may be silently broken — a prospect
filling it out could be getting no response. Treat as revenue-impacting.
The Playwright report (screenshots + traces) is attached to the run as an artifact.
Failure messages decode as follows:
FORM DID NOT SUBMIT— clicking submit fired no request to Brevo.Broken page JS or unwired handler (the June 2026 failure mode).
BREVO HTTP ERROR <status>— the request fired but Brevo returned an error.Check whether the Brevo form still exists / the endpoint URL changed.
BREVO RESPONSE NOT JSON— endpoint is not behaving like a Brevo form(redirect, HTML error page, moved URL).
BREVO REJECTED SUBMISSION— 2xx butsuccess:false; body included in the message.confirmation never appeared.
See the "Form Monitoring" section of the README.