Skip to main content

Workflow Execution Logs in Kyrios

Execution Logs provide a detailed, action-by-action record of what occurred inside a workflow, including successes, waiting states, errors, and exact execution timing.

Updated over 2 months ago

Who This Is For / When to Use

Use Execution Logs when you need to:

  • Diagnose why a workflow action failed or stalled

  • Confirm whether an email, SMS, Slack message, or update executed

  • Identify where a contact exited a workflow

  • Review action timing with timezone accuracy


What Execution Logs Show

Execution Logs display every action execution for a workflow.

They focus on:

  • Individual workflow actions

  • Execution status and errors

  • Timestamps with timezone

  • Contact-specific execution history

They do not show enrollment timing or entry conditions.


How to Access Execution Logs

  1. Go to Automations.

  2. Open Workflows.

  3. Select a workflow.

  4. Click the Execution Logs tab.


Execution Logs Table Overview

Each row represents one action execution for a contact.

Columns Explained

  • Contact
    The contact associated with the action

  • Action
    The custom name assigned to the workflow step

  • Status
    Indicates the execution result:

    • Executed

    • Waiting

    • Finished

    • Error

  • Executed On
    Exact timestamp with timezone

  • Actions
    Icons for deeper inspection and navigation


Execution Time and Timezone Visibility

All timestamps include the timezone in which the workflow executed.

This helps with:

  • Auditing time-sensitive automations

  • Comparing logs across regions

  • Aligning workflow timing with external tools


Filtering Execution Logs

You can filter execution data using the top filter bar.

Available Filters

  • Date range (up to 30 days)

  • Action type

  • Execution status

  • Specific contact

Filters make it easier to isolate:

  • Failed actions

  • A single contact’s activity

  • A specific automation step


Action Name vs Action Type

The Action column shows the custom name you assigned in the builder.

Hovering over the action reveals the actual action type.

Example

  • Custom name: “Notify Sales”

  • Actual type: Slack Message

This prevents confusion when workflows use descriptive naming.


Error Visibility in Execution Logs

Errors are clearly highlighted in the Status column.

Error rows

  • Are visually distinct

  • Surface the issue immediately

  • Always include a View Details link


Viewing Action Details

Click View Details to open the Event Details panel.

What You’ll See

  • Contact name

  • Action type

  • Event status (Success / Error)

  • Error messages (if applicable)

  • Metadata related to the execution

This is the primary tool for troubleshooting failures.


Highlighting the Selected Row

When you open details for an action, that row is automatically highlighted.

This helps you:

  • Keep context while scrolling

  • Avoid reviewing the wrong action

  • Track exactly what you’re analyzing


Viewing Execution History for a Single Enrollment

You can drill into one specific enrollment for a contact.

This view shows:

  • Only actions from that enrollment

  • Clear breadcrumb navigation

  • Focused execution context


Viewing Contact History Across Enrollments

You can also view all workflow executions for a contact, across multiple enrollments.

This is useful when:

  • A contact entered the same workflow multiple times

  • You need a full automation audit for one contact


Navigating Back to the Workflow Builder

From Execution Logs, you can jump directly back to the workflow action.

Go To Action allows you to:

  • Open the exact step in the builder

  • Make corrections quickly

  • Reduce troubleshooting time


Pagination in Execution Logs

Execution Logs support pagination for large workflows.

You can display:

  • 10 rows

  • 25 rows

  • 50 rows per page

This affects only the current view.


Common Execution Statuses

Common statuses include:

  • Executed – Action completed successfully

  • Waiting – Action is queued or delayed

  • Finished – Workflow reached its end

  • Error – Action failed and requires review


Common Issues and Fixes

An action shows “Error”

  • Click View Details

  • Review the error message

  • Verify required fields, permissions, or integrations

An action is stuck in “Waiting”

  • Check for delays or rate limits

  • Review dependent steps or conditions

  • Confirm external services are connected

I don’t see expected actions

  • Adjust filters and date range

  • Confirm the workflow version is published

  • Verify the contact actually reached that step


FAQ

What are Execution Logs used for?

Execution Logs show exactly what actions ran inside a workflow, their status, and when they executed.

Do Execution Logs show enrollment timing?

No. Enrollment timing appears in Enrollment History, not Execution Logs.

How do I see why an action failed?

Click View Details on the error row to view the failure reason and metadata.

Can I see all actions for one contact?

Yes. Use View Contact History to see executions across all enrollments.

Can I export Execution Logs?

Execution Logs are view-only. Use filters and date ranges to narrow results for review.

How precise are execution timestamps?

All timestamps include timezone information for accurate tracking.

Did this answer your question?