Help Center
DocsWorkflows List
View and manage your automation workflows
Overview
Workflows let you automate repetitive tasks and processes in your CRM.
List View
The workflows page displays all workflows in your organization.
The workflows list shows each workflow as a row with key information visible at a glance. Use this view to monitor which workflows are running, review recent execution history, and quickly enable or disable automations as needed.
Columns
- Name — The workflow name and a brief description of what it does.
- Status — An active/inactive toggle showing whether the workflow is currently running. Active workflows have a green indicator; inactive workflows are grayed out.
- Trigger Type — The event or condition that starts the workflow (e.g., "Company Created", "Opportunity Stage Changed").
- Last Run — The date and time the workflow was last executed. Shows "Never" if the workflow has not yet been triggered.
- Actions — Quick-action menu for editing, duplicating, or deleting the workflow.
Activating and Deactivating Workflows
Control which workflows are live and processing events.
Each workflow has an active/inactive toggle directly in the list view. Click the toggle to switch a workflow on or off instantly. When you deactivate a workflow, it stops processing new trigger events but does not cancel any actions that are already in progress.
Active Workflows
Active workflows listen for their configured trigger events and execute their actions automatically. A green status indicator shows that the workflow is live.
Inactive Workflows
Inactive workflows are paused and do not respond to trigger events. Use this state when you want to temporarily stop a workflow without deleting it, or while you are still building and testing the workflow.
Workflow Execution Timing
How and when workflows run after being triggered.
Workflows execute shortly after their trigger event occurs. Event-based triggers (such as record creation or stage changes) fire within seconds of the triggering action. Time-based triggers run on their configured schedule.
- Event-based execution — Triggers fire as soon as the matching event occurs (e.g., a new company is created). Actions are executed sequentially in the order they are defined.
- Scheduled execution — Time-based workflows run at their configured intervals. The Last Run column shows when the workflow last executed.
- Action ordering — Actions within a workflow run in sequence from top to bottom. If one action fails, subsequent actions may still execute depending on the workflow configuration.
Workflow Run Statuses
The detail page lists every execution of the workflow with one of the statuses below.
- Running — Actions are currently executing. Refreshes to a terminal status when the run finishes.
- Completed — Every action in the run succeeded.
- Failed — The run halted because a critical action failed and no retry was queued.
- Partial Failed — Some actions succeeded but at least one failed permanently and no retry was queued. Surfaces an amber badge so you can manually retry the failed actions from the run detail.
- Retry Pending — One or more actions hit a transient failure (network blip, third-party 5xx, rate limit) and have been queued for automatic retry. The retry queue cron picks them up every 5 minutes with exponential backoff — you don't need to do anything.
Automatic Retry Queue
Transient failures are retried automatically; permanent failures wait for manual action.
Laureo classifies every action failure as either transient(something that might succeed on a second attempt — a 502 from a third-party API, a timeout, a network glitch) or permanent(an invalid field, a deleted record, a logic error that another retry won't fix). Transient failures get enqueued into the workflow retry queue, which a background cron job processes every 5 minutes with exponential backoff. Each retry attempt is appended to the execution log so you can see exactly when and why the action eventually succeeded or gave up.
Manually Retrying Failed Actions
Force a retry from the workflow run detail page for runs that need operator attention.
On any workflow detail page, expand a run with status Partial Failed or Failed to surface the per-action log. Two retry buttons are available:
- Retry failed actions — The run-level button. Re-runs every failed action attached to that execution in one batch. Use this when you've fixed an upstream cause (corrected a record, restored a connection, raised an integration limit) and want everything to retry at once.
- Retry (per-action) — The inline button next to each failed action entry. Re-runs just that single action. Use this when only one action in a multi-step workflow needs a second chance.