Gravity Forms Flight Logs

Gravity Forms Flight Logs gives you a proper record of what Gravity Forms and its add-ons did on any request. Instead of a flat text file that is awkward to read and easy to lose, events are written in a consistent structure with request and trace correlation. Every event tied to one submission can be followed in order, even when more than one feed or integration runs on the same form.

That correlation helps most when something breaks. Logs live in the database and open in a viewer inside the WordPress admin, so you can search and inspect them without pulling files off the server. If a feed fails quietly, an integration stops firing or a submission misbehaves, you can read the sequence of events and work through it instead of guessing at the cause.

Features

• Structured log entries: Events are recorded in a consistent structure instead of unformatted text, so entries can be scanned and filtered rather than simply read line by line.
• Request and trace correlation: Every event from a single request is linked together, so the full sequence behind one submission can be followed in the order it happened.
• Database storage: Logs are kept in the database instead of loose files on disk, so they stay available without needing access to the server.
• Built-in admin viewer: Browse, search and open individual log entries from the WordPress admin, with no file transfers and no separate external tool required.
• Add-on activity visibility: See what Gravity Forms add-ons and feeds are doing during a submission, which covers more ground than the form itself.
• Faster debugging: A vague report such as "the feed did not run" becomes a traceable sequence of events, which cuts the time spent reproducing problems.
• Detail for problem reports: The log gives you a specific record to share when reporting an issue, in place of a loose description of the symptom.
• Fits your existing setup: Logging is added to the forms and integrations you already run, and it does not change how they behave.

Best for

• Developers debugging Gravity Forms feeds and integrations
• Agencies maintaining client sites with several form add-ons
• Site owners chasing down failed form submissions