Blue Raven refuses a submission in three places, and they fail differently. Knowing which one refused it is most of the fix, because each has a different cause and only one of them is usually a bot.
The three checks
The honeypot. A field nobody can see, with a name a bot recognises and a person never fills. A browser autofill that decides it is a phone number field can fill it, which is the one way a real person trips this check.
The signed timestamp. The form carries a token signed over the time and the form id. A submission that arrives in under three seconds is refused, because a person cannot read a form and fill it in that quickly. A submission older than two hours is refused as well, because a page left open overnight has a stale token.
The CAPTCHA. Turnstile, reCAPTCHA version 2 or version 3, or hCaptcha, if you configured one. This is the check that depends on somebody else's service, so it is the one that fails when keys are wrong or the provider is unreachable.
Which one was it
The archive only stores what passed, so a refused submission leaves no row behind. That makes the first check a simple one. If the entry is missing, a check refused it rather than the mail path losing it. The form list shows a blocked count that moves every time a check says no, so a refusal is visible even though nothing was stored.
That narrows it quickly. A missing entry means one of the three checks refused it, and the counter tells you which form did it. The honeypot and the timestamp are the two a browser can trip by accident.
Testing without switching everything off
Refusals are counted, so a test is measurable. Fill the form in a private window, wait a few seconds, and submit. Then look at the count and at the archive.
Change one thing at a time. Turning all three checks off and finding that the form works tells you nothing you can act on, and it leaves the form unprotected while you decide what to do next.
When it is a real person
The timestamp floor catches people who paste a filled form into a new tab and press submit immediately, which is rare but real. Three seconds is short enough that the normal case is unaffected.
The honeypot is the more likely one. A password manager or a browser's own autofill can fill hidden fields, and it does it more often on a form that asks for an email address and a name. If one person is repeatedly refused and everybody else is fine, their browser is the variable.
The CAPTCHA is the third. If the keys were pasted with a trailing space, or the domain was registered against the wrong site in the provider's dashboard, the widget renders and the check fails every time. The fix is in the provider's dashboard rather than in the plugin, and the diagnostics screen says which provider is configured.
What not to do
Do not remove the checks to make one submission work. A form with no spam check on a site with any traffic collects more junk than real mail within a week, and the junk goes to the same inbox as the real thing.
Do not raise the timestamp ceiling either. Two hours is already generous, and a longer window only lets a stale token through.
The Blue Raven plugin page has the full list of what the forms do, and sending the mail itself is a separate problem with its own article.
EnterraHost