A Ninja Forms success message does not prove that an entry was saved in WordPress. The form needs an enabled Record Submission action for local submission storage. Email, redirects, and other actions have separate jobs, so a working notification is not evidence that the database contains the same record.
If the entry exists but its notification is missing, follow the email delivery diagnosis. Stay here when the Submissions screen is empty or specific fields have disappeared.
Confirm the Form You Are Inspecting
Start at the public page where the inquiry was submitted. Record the embedded form's identity, the page URL, and a safe test reference. Check that you are inspecting that same form in the same WordPress environment. Duplicated forms, staging pages, and old shortcodes can make a correct submission look missing.
Use a small new test, then check the relevant form selection and any available date or search filters in Ninja Forms > Submissions. A filtered list can hide a record without deleting it. Record the timezone used for the test time rather than searching only one calendar date around midnight.
Inspect Record Submission
Open the form's Emails & Actions area and inspect Record Submission. The official action documentation explains its enable switch, field-selection behavior, and expiry settings. If the action is absent or disabled, enabling it now can help future submissions; it cannot recreate historical values that were never stored.
Check whether Save All or Save None is selected and how the Except list changes that selection. Missing individual fields may be deliberate storage exclusions rather than a failed insert. Decide which fields the business genuinely needs before changing the configuration. Do not start retaining sensitive data merely because storage is available.
Explanatory test plan. Record your own observations; no customer results are shown.
Separate Missing Records From Expired Records
Review the action's advanced retention setting. Ninja Forms documents that expiration applies to previous submissions from the same form that exceed the configured duration, not only new submissions. Treat a change to that setting as a data-retention decision with an owner, not a harmless troubleshooting toggle.
Do not shorten the interval experimentally on a live form. If you suspect deletion, preserve the current configuration and backup inventory before making further changes. Check whether the business intended that retention policy and whether it needs to retain the data at all.
| Symptom |
Evidence to investigate |
| Every new entry missing |
Correct form, action enabled, submission response |
| Some fields missing |
Save mode and field exclusions |
| Only older entries missing |
Expiration policy and backup dates |
| Email exists, no local entry |
Independent mail and storage actions |
| Entry exists, CRM empty |
Connector outcome and downstream record |
Test the Entire Action Sequence
Use a new harmless entry after recording any approved change. Confirm that the form returns the expected response and a matching local record appears with the fields you chose to retain. If it still fails, capture the browser submission request status and the corresponding server error at the same timestamp.
Test integration behavior separately. An external CRM could contain the lead even when local storage failed, or the reverse. The lead handoff guide explains how to trace that boundary without blindly replaying submissions.
Recover Only From Evidence That Exists
Possible recovery sources include an existing backup, a delivered notification, or an authorized downstream system. None is guaranteed to contain every field. Restore a backup into an isolated recovery environment first; replacing the current production database can overwrite newer inquiries, orders, and settings.
Record the source and confidence of reconstructed entries. Do not fabricate submission times or claim an email is a complete database record. De-duplicate against current entries and CRM records before any import. Keep access restricted and follow the organization's retention rules.
If local storage is failing on a business-critical form, HandL WP can help inspect the action configuration and recover available records. Bring the form ID, a recent test time, and the oldest date for which entries are unexpectedly missing.
Sources checked September 26, 2026. Visuals and examples are explanatory, not customer measurements.