Gravity Forms
+ Submission Inspector

A visitor says they filled in your form but nobody got the e-mail. A notification that worked last month stays silent for some entries. An entry lands in spam and you do not know which check put it there. Gravity Forms makes a lot of decisions after Submit, and most of them leave no trace you can read. The Gravity Forms Submission Inspector add-on records the decisions Gravity Forms actually made for a submission and explains them in plain language.

Switch tracing on for one form or any form, for the next few submissions and a time limit; it switches itself off. Each traced submission gets an explanation: which spam check marked it (honeypot, the anti-spam time check, link detection, a captcha, Akismet or a named plugin callback), which fields failed validation and with which message, even when no entry was created, why each notification was sent or not (its conditional logic rule by rule, its routing, or the plugin callback that disabled or changed it), which confirmation was chosen and why, which feeds ran, were skipped by their condition or were delayed, and where a submission stopped when a PHP fatal error ended it.

The Would it fire now? button checks an existing entry against the form as it is set up today, without sending an e-mail, running a feed or saving anything. Field values are never stored: a value that a rule compared is kept as its kind, length and a salted fingerprint, so the explanation can say "did not match" without showing it. Only administrators can unmask a value; it is read from the live entry for that one view and every unmask is logged. With tracing off, nothing is hooked into your submissions. For Gravity Forms 2.9 and newer.

While a tracing rule runs, the add-on listens to the decisions Gravity Forms makes during a submission: the spam check, validation, each notification (disabled, conditional logic, routing, sending), the confirmation it chose and the feeds it processed. When a plugin callback changes one of those decisions, the add-on notes its name and the plugin it belongs to, without changing what the callback receives or returns or the order in which callbacks run. When the request ends, the decisions become a trace in the add-on's own table: names, rules and masked values only, never a submitted value, deleted after 30 days by default. A tracing slot is taken with a single atomic database update, so parallel submissions never exceed the number you chose. Unlike configuration checks such as our Form Health add-on, it looks at what really happened to a submission; unlike our Form Speed Profiler it explains decisions rather than timings; Feed Health handles failed feeds and retries, Test Mode handles test runs, and SMTP / Email Tracking shows what happens after an e-mail is handed over. Everything runs on your own server — no outside HTTP request beyond the licence and update checks.