Skip to main content

Workflow Execution

When a CRM event matches your workflow’s trigger conditions, Thread automatically creates a run - an instance of the workflow executing for a specific account. [SCREENSHOT: Workflows page showing runs tab with recent executions] Caption: The runs tab shows all workflow executions with status and timing

How Workflows Execute

Automatic Triggers

Active workflows respond to CRM events in real-time:
  1. CRM event occurs (deal reaches stage, status changes, etc.)
  2. Thread receives webhook from the CRM
  3. Workflow starts - creates run, extracts account data
  4. Nodes execute sequentially until complete or paused
Workflows process CRM events within seconds. If you update a deal in HubSpot and the workflow is active, you’ll see a new run almost immediately.

Manual Triggers (Testing)

You can also manually trigger workflow runs for testing:
  1. Open the workflow editor
  2. Click “Test” in the toolbar
  3. Select or create test data
  4. Click “Run Test”

Run States

StateIconMeaning
Running🔵Workflow is actively executing
Paused⏸️Waiting at a human task node
CompletedSuccessfully reached an End node
FailedError occurred during execution
Cancelled🚫Manually cancelled by admin

State Transitions

Running → Paused (at human task)
Running → Completed (reached End node)
Running → Failed (error)
Paused → Running (human task completed)
Any state → Cancelled (manual)

Viewing Runs

From Workflows Page

The Runs tab on the Workflows page shows all recent runs across all workflows: [SCREENSHOT: Runs tab showing list of recent workflow runs] Caption: View all recent runs with account, workflow, status, and timing Columns:
  • Account - Company the run is for
  • Workflow - Which workflow ran
  • Status - Current state
  • Started - When the run began
  • Duration - Total time (or time so far)
  • Current Node - Where the run is (if not completed)

Run Detail View

Click any run to see detailed execution information: [SCREENSHOT: Run detail view showing execution path and node statuses] Caption: The run detail view shows exactly what happened at each step What you’ll see:
  • Visual path through the workflow
  • Status of each node (completed, skipped, current)
  • Data at each step
  • Time spent at each node
  • Error details (if failed)

Debugging Failed Runs

When a run fails, you’ll see:
  1. Red failed status on the run
  2. Error indicator on the failing node
  3. Error details in the run detail view

Common Failure Causes

Symptom: Node fails with “required field missing” errorCause: CRM record doesn’t have expected dataFix:
  • Add condition node to check for required data
  • Update CRM record and retry
  • Make the field optional in node config
Symptom: Node fails with “authentication error”Cause: CRM integration token expired or revokedFix:
  • Go to Connectors and reconnect the integration
  • Retry the run
Symptom: Node fails with “variable not found” errorCause: Node references variable that wasn’t setFix:
  • Check upstream nodes are configured correctly
  • Ensure conditional paths set required variables
  • Add default values where appropriate
Symptom: Send Email node failsCause: Invalid email address, rate limits, or email service issueFix:
  • Verify recipient email addresses
  • Check email service status
  • Retry after brief delay

Retrying Failed Runs

1

Open Run Detail

Click on the failed run to view details.
2

Identify Issue

Check the error message and failing node.
3

Fix Root Cause

Address the underlying issue (reconnect integration, update data, etc.).
4

Retry

Click “Retry” to re-execute from the failing node.
Retry re-runs from the failed node, not from the beginning. Previously completed nodes are not re-executed.

Managing Paused Runs

Runs pause when they reach human task nodes (CSM Assignment, Approval, Triage, Handoff Form).

Finding Paused Runs

From Runs tab: Filter by status = “Paused” to see all runs waiting for human action. From Queue Dashboard: Human tasks appear in the Queue Dashboard for team members to process. [SCREENSHOT: Queue dashboard showing paused workflow items] Caption: Paused runs appear as tasks in the Queue Dashboard

Completing Human Tasks

When you complete a human task in the Queue Dashboard:
  1. Task is marked complete
  2. Run automatically resumes
  3. Execution continues to next node
  4. Run completes or pauses at next human task

Queue Dashboard Guide

Learn how to process queue items

Cancelling Runs

To stop a run that’s in progress or paused:
1

Open Run Detail

Navigate to the specific run.
2

Click Cancel

Click the “Cancel Run” button.
3

Confirm

Confirm that you want to cancel. This action cannot be undone.
Cancelling a run stops execution immediately. Any pending human tasks are removed from queues. The account remains in whatever state it was in.

When to Cancel

  • Test run you no longer need
  • Duplicate run created by mistake
  • Run stuck due to unfixable issue
  • Account was created in error

Run History & Reporting

Viewing History

All runs are retained for auditing and analysis:
  • Filter by workflow - See runs for a specific workflow
  • Filter by status - Find completed, failed, or paused runs
  • Filter by date - Search within time ranges
  • Filter by account - See all workflow runs for an account

Key Metrics

Monitor these metrics to assess workflow health:
MetricWhat It Shows
Completion rate% of runs that reach End node
Average durationTime from start to completion
Pause timeTime spent waiting at human tasks
Failure rate% of runs that fail
Detailed analytics dashboard coming soon! Currently, you can export run data for analysis.

Real-Time Monitoring

Watching Active Runs

In the run detail view, you can watch execution in real-time:
  • Nodes highlight as they execute
  • Data updates appear immediately
  • Human task status shows when someone claims it

Notifications

Thread can notify you about workflow events:
  • Failures - Alert when a run fails
  • Long pauses - Alert when human tasks aren’t completed
  • Completions - Optional notification on success
Notification preferences are configured in SettingsNotifications.

Best Practices

Monitor Regularly

Check runs daily to catch issues early

Set Up Alerts

Get notified about failures immediately

Track Metrics

Watch completion rates and duration trends

Review Failures

Investigate every failure to prevent recurrence

Healthy Workflow Indicators

  • ✅ 95%+ completion rate
  • ✅ Human tasks completed within hours
  • ✅ No recurring failure patterns
  • ✅ Average duration within expectations

Warning Signs

  • ⚠️ Rising failure rate
  • ⚠️ Human tasks sitting for days
  • ⚠️ Same error appearing repeatedly
  • ⚠️ Runs taking much longer than expected

What’s Next?