Execution Logs

Execution Logs record rule execution attempts and delivery outcomes. Use this section when a PDF was not generated, a delivery action failed, or you need to confirm what happened after a form submission or manual test run.

Each top-level log represents a rule execution or skipped rule. Delivery actions, such as File Storage and Email, are stored as child logs and are easiest to inspect from the log detail modal.

Log Hierarchy

FormPDF PRO uses a parent/child log structure:

• Parent log: the rule-level result, such as a rule execution or skipped rule.
• Child log: a delivery-action result linked to the parent, such as File Storage or Email.

The default logs list shows top-level logs. Child delivery logs appear inside the detail modal for a parent log. When you filter by a specific action type, the list can show matching delivery-action logs directly.

Browse Execution Logs

Use this flow to find logs by date, status, action type, or keyword.

1. Open Dashboard > FormPDF PRO > Execution Logs.
2. Use Search to search log message text, form handles, or rule names.
3. Use Status to show All Statuses, Success, or Error.
4. Use Action type to show All execution types, File storage, or Email.
5. Use From and To to filter by date range.
6. Click Filter.
7. To clear filters, click Reset Filters.

The logs table shows:

• Date
• Source Form
• Rule applied
• Event
• Status
• Actions

Per-row actions:

• View Details opens the log detail modal. See View Log Detail.
• Delete Log permanently deletes the log. See Delete Logs.

Bulk action:

1. Select one or more log checkboxes.
2. Click Delete Selected.
3. Confirm the browser prompt.
4. The selected logs are permanently deleted.

View Log Detail

Use the log detail modal as the primary debugging tool. It shows the rule-level result and any delivery-action child logs in one place.

1. Open Dashboard > FormPDF PRO > Execution Logs.
2. Find the relevant log row.
3. Click View Details.
4. The modal loads the log detail content.

The modal shows:

• Status badge: Success or Failed.
• Execution time: the timestamp for the log.
• Event Type: the event type shown in monospace text.
• Duration: execution duration in milliseconds, when available.
• Execution message: the human-readable result message.
• Error details: JSON-formatted detail in a red error box, when available.
• Backend action results: child delivery logs, when present.
• Generated file reference: a link to the File Manager file detail page, when available.

Child delivery logs show:

• Delivery action label, such as File Storage or Email.
• Status badge.
• Duration in milliseconds, when available.
• Message.
• Error details, when available.

Failure state: if the log no longer exists, the detail request returns a not-found response and the modal shows an error message.

Delete Logs

Use delete actions only when you no longer need the diagnostic history. Deletion is permanent.

Delete One Log

1. Open Dashboard > FormPDF PRO > Execution Logs.
2. Find the log row.
3. Click Delete Log.
4. Confirm the browser prompt: “Are you sure you want to delete this log?”
5. The log is permanently deleted.
6. The page refreshes with a confirmation message.

The single-delete action is submitted securely with CSRF protection.

Bulk Delete Logs

1. Open Dashboard > FormPDF PRO > Execution Logs.
2. Select the checkboxes for the logs you want to delete.
3. Click Delete Selected.
4. Confirm the browser prompt: “Are you sure you want to delete the selected logs?”
5. The selected logs are permanently deleted.
6. The page refreshes with a confirmation message.

The bulk-delete action is submitted securely with CSRF protection.

What to Do When a Log Shows Failed

Start with View Details. The modal is the fastest way to determine whether the failure came from template rendering, delivery configuration, or the system environment.

1. Open the failed log with View Details.
2. Read Execution message first. It usually summarises the failure.
3. If Error details appears, expand your review there. The JSON can include technical details useful for a developer.
4. Check Backend action results:
   • If File Storage failed, inspect folder selection, filename pattern, file permissions, and whether the file manager can accept the generated file.
   • If Email failed, inspect recipients, submitter email attribute, subject/body tokens, attachment mode, and whether link mode depends on File Storage.
5. If there is no child delivery failure, review the rule and template:
   • Check whether the selected template still exists.
   • Check template tokens and HTML.
   • Check whether the rule's form and conditions match the submission you expected.
6. After fixing the underlying issue, run a manual test from the Rules page or use Run Again from the submission detail page. Do not use Run Again if the rule's template has been deleted until a developer has restored or repaired the rule.
7. Return to Execution Logs and confirm that the new log is successful.

Common Failure Categories

Category	What to inspect
Template issue	Missing template, invalid HTML, broken or unresolved tokens, external template path problems (e.g. path traversal prevention errors).
Delivery configuration issue	File Storage disabled when links require it, File Storage ordered after Email, invalid recipients, missing submitter email attribute, invalid filename generation (e.g. dot-only filenames), or invalid webhook URLs.
System issue	File Manager import errors, mail transport errors, permissions, missing underlying Express entry, unexpected server exceptions.