Run Log

How to access

Step 1 — Open the action bar (the global search/command bar at the top of the screen).

Step 2 — Type Run Log and press Enter or select Go to Run Log from the results.

Understanding the log

Each row in the log represents one automation execution. The columns are:

• ID — Unique identifier for the execution entry.
• Date — Timestamp of when the automation ran.
• Status — Result of the execution (e.g., successful, failed).
• Action name — The name of the automation action that was triggered.
• Webhook name — Name of the webhook associated with the automation, if applicable.
• Webhook token — Token identifying the webhook endpoint used.
• Action type — The type of action executed (e.g., nocode).
• Action related to — The ID of the record the automation acted on.
• Action relationship — Identifies the relational context of the execution.

Use cases and examples

• You notice a record wasn't updated as expected and want to confirm whether the automation actually ran.
• You want to audit how many times a specific automation has executed over a period.
• You're debugging a webhook-triggered automation and need to trace which token and action were involved.
• You want to verify that a scheduled automation is running daily without failures.

Keep in mind

• The Run Log only shows asynchronous automation executions — synchronous automations are not listed here.
• The log is read-only — you cannot re-run, cancel, or edit executions from this view.
• The log covers your entire organization, not just a single table or app.

FAQ

1- Can I filter or search the log for a specific automation?

Yes. Use the filter and search controls at the top right of the log table to narrow results by action name, status, date, or other fields.

2- Why is an automation I triggered not showing up in the Run Log?

The Run Log only tracks asynchronous automations. If your automation runs synchronously, it won't appear here.

3- Can I export the Run Log?

Yes. Use the download icon at the top right of the table to export the log data.

4- How far back does the Run Log history go?

The log retains historical entries, but the retention period may vary depending on your plan. Contact Jestor support for details specific to your organization.