Webflow: forms stop recording once the plan limit is hit
The form shows its success state to visitors, but the submissions list stops growing. Leads from a given day are simply absent, with no error anywhere the site owner would normally look.
- Webflow
- Forms & leads
Root cause, in plain English
Webflow site plans cap how many form submissions a site will store. On the free Starter plan that cap is fifty for the lifetime of the site. Once it is reached the endpoint stops collecting, returning a conflict or rate-limit response that the front end does not surface. Visitors still see the success message, so nothing about the page suggests the lead was discarded.
How to fix it
Open Site settings, then General, then Overview, and read the submission count against your plan's cap. If they match, the cap is the cause and every submission since then is gone.
Upgrade the site plan to resume collection, or move submission storage off Webflow entirely so the cap stops being a single point of failure.
Route submissions to a second destination as well — a webhook into your own store or an automation tool — so a full mailbox never means a lost lead.
Export the existing submissions and clear old ones if your plan counts stored rather than lifetime entries, then confirm a fresh test submission appears.
Add an end-to-end check that submits the form and verifies the lead arrived, rather than trusting the on-page success state.
Go deeper: the full guide to forms that accept and drop leads.
How Nightlamp detects this automatically
- Browser journey
- Email flow
- API canary
A browser_journey fills in and submits the real form on a schedule, then an email_flow or api_canary check asserts the lead actually arrived at its destination. That second half is the part that matters here: the form's own success message is rendered client-side and stays green long after the backend has stopped storing anything.
Catch this before your customers do
Nightlamp runs these checks continuously against your live app and sends a plain-English diagnosis — not a wall of logs — the moment this pattern shows up.
Related patterns
Frequently asked questions
- Why does the visitor still see a success message?
- The success state is shown by the page's own script once the request completes. It does not distinguish between a stored submission and a rejected one, so a capped site keeps reassuring every visitor that their message went through.
- Can I recover the submissions that were dropped?
- No. Submissions rejected at the cap are never stored, so there is nothing to export or restore. This is why the failure is expensive: it is silent, and the loss is permanent by the time anyone notices the list stopped growing.
- Does this affect paid plans too?
- Paid site plans have much higher limits and bill overage rather than dropping entries outright, so the hard silent stop is characteristic of the free Starter plan. Any plan can still fail this way if a script or bot burns through the allowance.
Newsletter
Get new incident patterns as we publish them
One email when new failure patterns, fixes, and monitoring recipes for no-code and AI-built apps land. No fluff, unsubscribe any time.
Double opt-in. One-click unsubscribe. No spam, ever.