Krom Automation records every workflow execution in the database and gives you three views into that data: the Logs page for individual execution records, the Analytics view for aggregated performance trends, and the Reports page for filtered, exportable data.

This page covers how to use all three, what each piece of data means, and how to use logs effectively for troubleshooting.

The Logs page #

Go to Krom Automation > Logs to see a searchable, filterable list of every workflow execution recorded on your site.

Each row in the logs list shows:

Column	What it shows
Timestamp	When the execution started
Workflow	The name of the workflow that ran
Trigger	Which trigger fired to start the execution
Entity	The user, post, or order that triggered the event
Status	Whether the execution succeeded, failed, or partially completed
Duration	How long the full execution took to complete

Filtering and searching logs

You can filter the logs list by workflow name, trigger type, status (success, failed, or all), and date range. Use these filters to narrow down a large log history when you’re looking for a specific execution or investigating a pattern of failures.

Searching by entity lets you find all executions related to a specific user ID, post ID, or order ID. This is useful when a user reports an issue and you want to see exactly which automations ran for them.

Execution statuses

Success: All steps in the workflow completed without errors.

Failed: One or more steps encountered an error. The workflow still ran to completion — a failing step does not stop the rest of the workflow. The execution is marked as failed if any step failed.

Partial: The workflow ran but some steps were skipped because a condition routed the execution down a branch with no actions attached.

Reading an execution detail #

Click any log row to open the full step-by-step execution trace for that run.

The detail view shows every step the workflow took, in order. For each step you can see:

Input data: The exact data the step received, including all resolved merge tags. This is what the action actually worked with, not what you typed in the configuration. If a merge tag resolved to empty, you’ll see it here.

Output: What the step produced or returned. For a Send Email action, this shows the final resolved subject line and message body. For an HTTP Request action, this shows the response status code and body. For an AI Generate Text action, this shows the text the AI returned.

Execution time: How long that individual step took in milliseconds.

Error messages: If a step failed, the specific error message appears here. This is your starting point for debugging.

The most useful thing about execution detail

The execution detail view shows you the actual resolved merge tag values, not the template placeholders. If you wrote Hi {{first_name}}, and the email actually sent as Hi , with nothing after the comma, the execution detail will show you that first_name resolved to an empty string. That tells you the user had no first name stored in meta, not that the merge tag syntax was wrong.

Always read the input data for a failing step before changing the workflow configuration. The answer to most workflow problems is in the execution detail.

Node-level statistics #

Inside the workflow editor, each action node displays its own execution statistics. Click any action node on the canvas to see:

• Total number of times this specific step has run
• Number of successful executions through this step
• Number of failures on this step

This lets you identify which specific action in a long workflow is responsible for failures, without having to scroll through many execution logs manually. If a workflow has 50 executions and one action node shows 12 failures, that’s immediately visible from the canvas.

The Analytics view #

The Analytics view shows aggregated execution data over time. Go to Krom Automation > Analytics to access it.

The dashboard metrics at the top of the Analytics page show:

Metric	What it tells you
Total Workflows	The number of workflows on your site (active and paused combined)
Active Workflows	How many workflows are currently set to Active
Total Executions	The total number of workflow runs recorded across all time
Executions This Week	Executions recorded in the last 7 days
Success Rate	The percentage of executions that completed with all steps succeeding
Failed Executions	The total count of executions that had one or more failing steps

Below the metrics, the analytics charts show:

Executions over time: A bar chart showing how many executions ran per day, week, or month. Use this to spot spikes in activity (a campaign went out, a WooCommerce sale drove a lot of orders) or unexpected drops (a workflow was paused or a trigger stopped firing).

Success vs. failure breakdown: A view of how many executions succeeded versus failed. A rising failure rate is an early warning that something has changed — a third-party API started rejecting requests, a merge tag stopped having data, or a plugin update changed a hook’s behaviour.

Most active workflows: Which workflows run most frequently. Useful for understanding where the automation activity on your site is concentrated.

Trigger frequency: Which triggers are firing most often. Useful for capacity planning and for spotting triggers firing unexpectedly.

The Entity Timeline #

For any specific user or order, you can view a timeline of all automation events that occurred for that entity.

Navigate to the entity timeline by finding an execution in the Logs page and clicking on the entity reference, or by visiting the entity timeline endpoint directly.

The timeline shows every workflow that ran for that entity, in chronological order, with the outcome of each execution. This answers the question: “What automations has this specific user experienced?” It’s particularly useful when a user contacts support about an email they received (or didn’t receive) and you need to trace their exact automation history.

The Reports page #

The Reports page at Krom Automation > Reports provides a filtered and exportable view of your execution data. It gives you the same underlying data as the Analytics view but with more control over the time range and scope.

Filters

Filter	What it controls
Date range	Restrict the report to a specific start and end date
Workflow selector	Show data for one specific workflow or all workflows
Trigger type	Filter by which trigger caused the executions
Status	Show only successful executions, only failed ones, or all

Charts on the Reports page

Executions over time: A line or bar chart of daily execution volume across your selected date range.

Per-workflow breakdown: A breakdown of which workflows accounted for what share of total executions in the selected period.

Success rate trend: How your overall success rate changed over the selected period. A sudden dip on a specific date usually points to a specific event worth investigating.

Exporting to CSV

Click the Export button on the Reports page to download the current filtered view as a CSV file. The export includes all columns visible in the report and respects the active filters, so what you see is what you get in the file.

The CSV export is useful for:

• Bringing execution data into a spreadsheet for custom analysis
• Sharing automation performance data with a client or team member
• Archiving report data before clearing logs to reclaim database space

Using logs to debug a workflow problem #

When a workflow isn’t behaving as expected, follow this sequence:

Step 1. Go to Krom Automation > Logs and find the most recent execution of the affected workflow. Check its status.

Step 2. Click into the execution to open the detail view. Read each step’s input data in order. Find the first step that either failed or produced unexpected output.

Step 3. Look at the input data for that step. Check whether merge tags resolved to the values you expected. An empty value where you expected a name or email is usually the problem.

Step 4. Read the error message on any failed step. Most error messages are specific enough to point directly to the fix.

Step 5. If you need more detail, enable Debug Mode in Krom Automation > Settings > Logging and Cleanup, trigger the workflow again (by registering a test user, creating a test post, or using the REST API to manually trigger it), then re-read the log with the additional debug data.

Step 6. Fix the configuration and run a simulation before re-activating the workflow.