Troubleshooting
Start with Test connection (Settings → Connection) or wp formsieve test: it reports your plan, this month's AI checks, this site's slot, the model, the latency and the request ID, and names the problem. The dashboard shows the circuit-breaker state and the last error, and Formsieve keeps the last 50 API errors (never your key or visitor text) for support.
Each state below shows as a notice in the plugin with a link to your account at https://formsieve.com/account/. In every one of them your forms keep working: the free local checks still run, and a submission the AI could not check is delivered (or held for review, if you chose Hold for review under When the AI check cannot answer). Formsieve never sends a submission to spam because of your plan.
"Key not accepted"
Formsieve's service does not know the key, or the key was revoked or disabled (HTTP 401 invalid_key or 403 key_revoked).
- Copy the key again from your account, without spaces. Keys look like
FS-XXXX-XXXX-XXXX-XXXX. - A key defined in
wp-config.php(FORMSIEVE_API_KEY, or until version 1.2.0 the earlier plugins'FSV_GF_API_KEYorFSV_CF7_API_KEY) wins over the one saved in the settings, so checkwp-config.phptoo. - After a key rotation in your account, the previous key keeps working for 24 hours; paste the new one before then.
- A key is revoked after a full refund of a payment for its current subscription, after a withdrawal, or when a payment dispute is decided in your favour, and disabled while a payment dispute is open.
After this error Formsieve pauses calls for 60 minutes, so a wrong key cannot generate a stream of failing requests. Save the corrected key and run Test connection to confirm it works. Submissions in the meantime are noted "Not checked by AI: the Formsieve key was not accepted" and delivered, also when the fail mode is Fail closed.
"No active Formsieve plan" or "trial ended"
The trial is over (14 days or 500 AI checks, whichever came first) and the key has not moved to the Free plan yet, or the subscription lapsed or was cancelled (HTTP 402 subscription_inactive). A trial key moves to the Free plan within about 5 minutes of the trial's end (as of 2026-09-29). Subscribe or renew in your account; the same key starts working again, usually within a minute. Formsieve asks again at most every 15 minutes, and Test connection checks at once.
"This site is not on your Formsieve plan"
The key already serves as many production sites as the plan allows, or this site already used a trial (HTTP 403 site_not_allowed). Remove a site you no longer use in your account (Sites), or upgrade. After a downgrade, the sites added most recently are the ones refused. Staging and development sites never use a slot on the trial and the paid plans. On the Free plan (as of 2026-09-29), the AI check is off on development and staging sites ("The Free plan covers one production site, so the AI check is off on this development or staging site."), and a site that used a free allowance with another key is refused ("This site already used a free Formsieve allowance with another key, so the AI check is paused here."). See Sites and agencies.
"AI checks paused: the monthly allowance is used"
Your sites reached the plan's ceiling for the month, or the allowance after going over it two months in a row (HTTP 429 quota_paused). Checks resume on the 1st (00:00 UTC) or at once after an upgrade. See Plans, AI checks and limits.
On the Free plan (100 AI checks a month for one production site, as of 2026-09-27), the notice reads "You've used this month's 100 free AI checks. AI checks resume on … (UTC). …", and submissions are noted "Not checked by AI: this month's free AI checks are used". AI checks resume on the 1st (00:00 UTC), or when you choose a paid plan in your Formsieve account.
"AI checks paused under the fair-use limit"
What you see. Test connection says "AI checks paused: fair-use limit reached". The notice on Formsieve's screens reads "AI checks are paused until … at 00:00 UTC under the fair-use limit: this month your forms sent far more text to the AI check than typical contact forms. …", with the 1st of next month as the date. On a trial it reads "AI checks are paused under the fair-use limit: your trial's forms sent far more text to the AI check than typical contact forms. …". Each submission gets the note "Not checked by AI: paused under the fair-use limit".
Why. Next to its monthly AI checks, each key has a monthly fair-use limit on the amount of submission text the AI processes (as of 2026-09-27). It is not a number of AI checks, so it can pause AI checks while the meter still shows checks left. It is reached when a key's forms send far more text than typical contact forms, for example very long, padded or machine-generated text, which often comes with a spam wave (HTTP 429 quota_paused, reason fair_use). On a trial the limit covers the whole trial and does not reset.
Your forms. They keep working, and the free local checks keep running. Submissions that pass them are delivered with the note above, or held for review if you chose Hold for review under When the AI check cannot answer. Fail closed does not apply, and paused answers do not count as AI checks.
What to do.
- On a paid plan or the Free plan, AI checks resume on their own on the 1st (00:00 UTC). Formsieve asks again every 15 minutes.
- Look at Formsieve → Log for long or repeated messages. During a spam wave, the per-form hourly limit and Aggressive mode send fewer submissions to the AI (During a spam flood).
- If your forms normally receive very long messages (application forms, for example), write to support@formsieve.com and we'll review the pause.
- On a trial, choose a plan in your Formsieve account to continue, or write to support@formsieve.com.
"AI checks paused until 00:00 UTC"
What you see. Test connection says "AI checks paused until 00:00 UTC", and the notice reads "AI checks are paused until 00:00 UTC: this key reached today's limit on AI processing. …". Each submission gets the note "Not checked by AI: paused until 00:00 UTC".
Why. Each key also has a daily limit on AI processing, so that one key cannot use up capacity that all Formsieve customers share (as of 2026-09-27). It is reached after unusually high use in one UTC day, such as a large spam wave (HTTP 429 quota_paused, reason daily_share).
Your forms. They keep working, and the free local checks keep running. Submissions that pass them are delivered with the note above, or held for review if you chose Hold for review under When the AI check cannot answer. Fail closed does not apply, and paused answers do not count as AI checks.
What to do. Nothing: AI checks resume on their own at 00:00 UTC, and Formsieve asks again every 15 minutes. During a spam wave, the per-form hourly limit and Aggressive mode send fewer submissions to the AI (During a spam flood). If it happens on an ordinary day, write to support@formsieve.com.
"AI checks paused: the Free plan's capacity is used for now"
What you see. Only keys on the Free plan get this. Test connection says "AI checks paused: the Free plan's capacity is used for now", and the notice reads "AI checks on the Free plan are paused: the Free plan's capacity is used for now. They resume on their own at 00:00 UTC, on … at the latest. Forms keep working and the free local checks keep running.", with the 1st of next month as the date. Each submission gets the note "Not checked by AI: the Free plan's capacity is used for now".
Why. All Free keys share a limited AI capacity for each day and each month (as of 2026-09-27). When this day's or this month's Free capacity is used, AI checks on Free keys pause, even if your key still has Free AI checks left this month (HTTP 429 quota_paused, reason free_pool). Paid plans are not affected.
Your forms. They keep working, and the free local checks keep running. Submissions that pass them are delivered with the note above, or held for review if you chose Hold for review under When the AI check cannot answer. Fail closed does not apply, and paused answers do not count as AI checks.
What to do. Wait: AI checks resume on their own at 00:00 UTC, on the 1st of next month at the latest. Or choose a paid plan in your Formsieve account (the notice's See plans link): the same key resumes AI checks once the plan is active. Test connection checks at once; otherwise Formsieve asks again within 15 minutes.
"AI checks on the Free plan are paused for now"
What you see. Only keys on the Free plan get this. Test connection says "AI checks on the Free plan are paused for now", and the notice reads "AI checks on the Free plan are paused for now. Forms keep working, submissions are delivered and noted "Not checked by AI", and the free local checks keep running." Each submission gets the note "Not checked by AI: the Free plan's capacity is used for now".
Why. Formsieve has paused AI checks for every Free key to protect the service (HTTP 429 quota_paused, reason free_paused). This pause has no set end: it lasts until Formsieve lifts it (as of 2026-09-27). Paid plans are not affected.
Your forms. They keep working, and the free local checks keep running. Submissions that pass them are delivered with the note above, or held for review if you chose Hold for review under When the AI check cannot answer. Fail closed does not apply, and paused answers do not count as AI checks.
What to do. Nothing: AI checks resume on their own when the pause is lifted, and Formsieve asks again every 15 minutes. To resume AI checks now, choose a paid plan in your Formsieve account (the notice's See plans link).
Service unavailable, timeouts and "Circuit breaker open"
Formsieve's service or the AI behind it did not answer in time (HTTP 503, 504 or a network error). Each check has a 3-second budget with at most one quick retry. After 5 failed calls within 5 minutes Formsieve stops calling for 10 minutes and then sends a single probe; if it succeeds, checks resume. These are outages: submissions follow your fail mode (delivered by default). A refusal under the service's own short-term limits is not an outage: see "Formsieve service limit reached for now" under Submissions noted "not checked".
If your host blocks outbound HTTPS, allow connections to api.formsieve.com. Formsieve uses the WordPress HTTP API, so a proxy configured for WordPress (WP_PROXY_HOST) is used automatically.
Submissions noted "not checked"
They were not checked by the AI. The note, "Not checked (…)" by Formsieve (Gravity Forms) or "Formsieve: not checked (…)" (Contact Form 7), or "Not checked by AI: …" for a plan state, shows why. Formsieve → Log can filter by these reasons.
| Text (log reason code) | What to do |
|---|---|
no Formsieve key, data-sharing consent not given (no_key, no_consent) |
Finish the setup wizard. Always delivered. |
Not checked by AI: no active Formsieve plan (service_inactive) |
See "No active Formsieve plan" above. |
Not checked by AI: this site is not on your plan (site_not_allowed) |
See "This site is not on your Formsieve plan" above. |
Not checked by AI: monthly allowance used (allowance_paused) |
See "AI checks paused" above. |
Not checked by AI: this month's free AI checks are used (free_allowance_paused) |
Free plan: see "AI checks paused: the monthly allowance is used" above. |
Not checked by AI: paused under the fair-use limit (fair_use_paused) |
See "AI checks paused under the fair-use limit" above. |
Not checked by AI: paused until 00:00 UTC (daily_share_paused) |
See "AI checks paused until 00:00 UTC" above. |
Not checked by AI: the Free plan's capacity is used for now (free_pool_paused) |
Free plan: see "AI checks paused: the Free plan's capacity is used for now" and "AI checks on the Free plan are paused for now" above. |
Not checked by AI: the Formsieve key was not accepted (key_invalid) |
See "Key not accepted" above. |
hourly cap reached (cap_hourly) |
Your per-form hourly limit was reached (Plans, AI checks and limits); raise it or wait. It counts every request sent, retries included. It follows the fail mode like an outage, because it is a limit you set. |
API temporarily paused after errors (breaker_open) |
See "Service unavailable" above. |
Formsieve service limit reached for now (service_limited) |
Formsieve's service refused the check for a moment: too many checks from this key or from this site in a short time, or the service paused AI checks for now. Test connection names it, for example "Key valid; too many checks from this key just now, try again in a minute". It passes on its own and does not open the circuit breaker. Delivered, or held for review if you chose Hold for review; never sent to spam, also with Fail closed. |
API unavailable (api_unavailable) |
Timeout, network or server error; see "Service unavailable" above. The dashboard's last error names the cause. |
The dashboard counts unchecked submissions in the last 24 hours. Fail open is the default on purpose: an outage should cost you a filtered inbox for a while, never a lead.
"Unrecognized model"
The service answered with a Jev version that Formsieve's thresholds were not set for. Filtering continues; see Calibration and consider Strict calibration.
"Update the plugin" or request rejected as invalid (HTTP 400, 413 or 422)
The service did not accept the request. This is never retried. A 422 about the question set means the plugin is older than the service supports: update it from Plugins. If it persists, send us the error and the request ID from the dashboard.
Nothing seems to be checked
- Are you logged in? Trusted users are allowed without a check (Trusted users; see Pre-filters). Test from a private browser window.
- Is Test mode on? A red badge shows in the admin bar; verdicts are simulated.
- Is the setup finished? Until a Formsieve key and consent are in place (or Test mode is on), the AI check does not run. The free local checks still run on both form plugins, and a submission they do not decide shows as a "not checked" row in the log.
- Is the form plugin found? The Dashboard lists the form plugins Formsieve found. Formsieve checks Gravity Forms 2.9 or later and Contact Form 7 6.0 or later; while the earlier Formsieve for Gravity Forms or Formsieve for CF7 is still active, Formsieve leaves that form plugin to it (Moving from the two earlier plugins).
- Is the form enabled? Check the form's Formsieve settings. On Contact Form 7, also check the Additional Settings tab for
formsieve: offanddemo_mode: on(Contact Form 7 then sends no mail and Formsieve does not check the form). - Did another tool decide first? On Gravity Forms: when Gravity Forms' honeypot, or another plugin that hooks into
gform_entry_is_spambefore priority 50, has already flagged a submission, Formsieve does not check it (Gravity Forms' Akismet check runs after Formsieve). On Contact Form 7: when Akismet, reCAPTCHA, Turnstile or the Disallowed Comment Keys check of Contact Form 7 has already flagged a submission, Formsieve does not check it. - Did a pre-filter decide? Open Formsieve → Log; the reason code shows which check decided (Reason codes).
The dashboard shows fewer submissions than the Log tab
The Log tab lists every decision, including re-checks from a Gravity Forms entry's Formsieve panel and WP-CLI samples (marked "Re-check" or "WP-CLI sample") and Test mode rows (marked "Test mode"). The Dashboard counts only what visitors submitted outside Test mode. Its API calls, tokens and cost do include the re-checks and samples, because they were billed (Plans, AI checks and limits).
A threshold I typed was not saved
The review and block thresholds (Settings → Detection → Sensitivity) accept a fraction such as 0.85 or a percentage such as 85 or 85%; 1 means 100%. Anything else (text, a negative number, more than 100) is refused with a message and the previous value stays. If the review threshold is not below the block threshold, the setting is saved with a warning, because then nothing can go to review.
A real lead was marked as spam
- Restore it: Not Spam on the entry (Gravity Forms), Not spam in Flamingo (Contact Form 7), or Mark not spam in Formsieve's log. Formsieve learns the sender.
- Look at the reason on the entry, in Flamingo's spam log or in Formsieve's log. If it came from a list or a heuristic, adjust that list. If it came from the model, consider the Low preset, or describe legitimate messages in the form's What legitimate submissions look like (Gravity Forms) or What this form is for (Contact Form 7) setting ("Suppliers often write to offer quotes").
- Keep When the AI check cannot answer on fail open and Review band on its default (deliver and tag the subject), so borderline messages still reach you.
After a salt change (moving the site or a security reset)
The stored key is obfuscated with your site's authentication salt. If the salts in wp-config.php changed (a migration or a security reset), the saved key cannot be read back and forms are not checked; an error notice says "The saved API key can no longer be read because the site's security salts changed". Enter the key again under Settings → Connection, or define it as a constant.
The same salt keys the hashes in the decision log and in the learned trusted and blocked lists. After a salt change, Formsieve can no longer match those older records to an e-mail address: Export Personal Data and Erase Personal Data do not find older log rows, and earlier learned senders stop matching (blocked senders go on to the other checks, and trusted senders are checked again). The older rows hold no readable address and are removed by the daily retention task. Let Formsieve learn again from your Spam and Not spam corrections.
Updates
Updates come from WordPress.org like any other plugin; see Installing from WordPress.org. A copy downloaded from your Formsieve account before 2026-10-14 gets no more updates: install the WordPress.org copy over it (Moving from a formsieve.com download). To have WordPress install them for you, tick Install Formsieve updates automatically (recommended) under Settings → Advanced (Install updates automatically). When that panel shows text instead of a box, the text says why: automatic updates are off for the whole site, your host or another plugin decides them, or your account cannot update plugins.
Asking for help
Write to support@formsieve.com with your WordPress, PHP and host-plugin versions (never your key), the Test connection result and, for a specific submission, the request ID shown on the entry.