Workflow Execution Logs

The Workflow Execution Logs page provides a detailed history of all workflow executions, showing when workflows ran, which leads were affected, what actions were taken, and whether they succeeded or failed.

Accessing Execution Logs

1. Navigate to Settings in the sidebar.
2. Click the Workflow Logs section.
3. The logs page displays a filterable, searchable table of all workflow executions.

Log Table Columns

Column	Description
Executed At	Timestamp of when the workflow execution occurred.
Workflow	The name of the workflow that executed.
Lead	The applicant that triggered the workflow, shown as a clickable link to their detail page.
Action	The action node type that was executed (e.g., Send Email, Move Stage).
Status	The execution result: triggered, executed, error, or rate_limited.

Filtering Logs

The logs page includes a comprehensive filter bar:

Date Range Filter

1. Click the date range button in the filter bar.
2. Select a start and end date using the date range picker.
3. Logs are filtered to show only executions within the selected range.

Workflow Filter

1. Use the workflow dropdown to filter by a specific workflow.
2. The dropdown includes all workflows (active and inactive) and supports search.

Status Filter

Filter by execution status:

Status	Meaning
Triggered	The trigger node matched and the workflow started.
Executed	An action node completed successfully.
Error	An action node failed with an error.
Rate Limited	The execution was blocked by rate limiting (too many executions in a short period).

Search

The text search field filters logs by lead name, workflow name, or other textual content.

Clearing Filters

Click the Clear button to reset all filters and show all logs.

Expanding Log Details

Each log row is expandable:

1. Click anywhere on a log row.
2. The row expands to show additional details:
   • Full execution context -- the data and parameters involved.
   • Error messages -- if the execution failed, the error details are shown.
   • Node information -- which specific node in the workflow was executed.

Understanding Execution Statuses

Triggered

The initial status when a trigger node matches an event. This confirms the workflow was activated. A "triggered" entry is always followed by one or more "executed" or "error" entries for the action nodes.

Executed

The action was performed successfully. For example:

• An email was sent.
• A lead was moved to a new stage.
• A note was added.
• A tag was applied.

Error

The action failed. Common causes:

• Email delivery failure -- the SMTP service rejected the email.
• Invalid target -- the target stage or status no longer exists.
• Permission error -- the system could not perform the action due to constraints.

TIP

When you see an error log, expand the row to see the detailed error message. This usually provides enough context to diagnose and fix the issue.

Rate Limited

The system detected a potential infinite loop or excessive execution frequency:

• Happens when workflows trigger each other in rapid succession.
• The rate limiter prevents runaway execution chains.
• The log entry includes context about why it was rate-limited.

WARNING

If you see rate-limited entries frequently, review your workflows for circular dependencies. A common pattern: Workflow A changes a status, which triggers Workflow B, which changes the status back, which triggers Workflow A again.

Linking to Lead Details

The Lead column in the log table contains clickable links:

• Click a lead's name to navigate directly to their detail page.
• If the lead has been deleted, the link appears as plain text with the lead's ID.

Log Retention

Execution logs are retained for auditing purposes. They are not automatically deleted, ensuring you have a complete history of all workflow activity.

Troubleshooting with Logs

Workflow Not Firing

If a workflow is not executing as expected:

1. Check the logs for any entries from that workflow.
2. If no entries exist, verify:
   • The workflow is active.
   • The trigger type matches the event you expect.
   • The trigger conditions (stage, form, status filters) are correctly configured.
   • The workflow is associated with the correct pipeline.

Workflow Firing Too Often

If a workflow is executing more than expected:

1. Filter logs by the workflow name.
2. Check the trigger conditions -- they may be too broad.
3. Add more specific conditions to narrow when the trigger fires.

Actions Not Taking Effect

If a workflow shows "executed" status but the expected changes are not visible:

1. Check if another workflow or manual action is overriding the change.
2. Verify the action configuration (correct target stage, status, template, etc.).
3. Check for error entries that might indicate partial failures.

Was this helpful?