Workflow Settings
Configure automation behavior.
Workflow settings control automation behavior for the workspace.
What You Can Configure
Workflow settings include:
- Workflow builder limits, such as active workflows, nodes, edges, schedules, webhooks, run rate, concurrent runs, and maximum run duration.
- Notification channels for workflow alerts.
- Notification events, such as failed runs, consecutive failures, schedule misfires, webhook authentication failures, and quota breaches.
- Alert throttle minutes.
- Detailed run log retention.
- Default misfire policy for scheduled automation.
Update Workflow Settings
- Open Settings.
- Go to Workflows.
- Review limits before increasing automation usage.
- Choose notification channels and events.
- Set retention for detailed run logs.
- Choose a misfire policy.
- Save settings.
Ownership And Alerts
Every production workflow should have an owner and a monitored alert path. The owner should know what the workflow changes, what failure means, and when to pause it.
Record the owner near the workflow description or internal process notes. When a workflow fails, the first question should be who can safely decide whether to pause, retry, or edit it.
Before Enabling Workflows
Confirm permissions, connected apps, notification channels, and required modules before enabling workflow automation broadly.
Start with alerting enabled for failures before publishing important workflows. The person responsible for the workflow should know where failed-run messages go and how long detailed logs are retained.
Also confirm the workflow owner can access the records, apps, and settings the workflow uses. A workflow can fail even when the builder is correct if the connected app expires, a module is disabled, or a role loses access.
Misfire Policies
- Skip missed runs: Ignore missed scheduled runs.
- Run one catch-up: Run one catch-up execution after downtime or delay.
- Run full catch-up: Run every missed execution. Use this only when the workflow can safely process backlog.
Choose Run full catch-up only for idempotent workflows that can process duplicates safely. For customer emails, invoices, messages, and record updates, use a safer policy unless you have tested backlog behavior.
Alert Setup
Turn on alerts for the events your team will actually act on:
- failed runs for critical workflows
- consecutive failures for provider or permission problems
- schedule misfires for time-sensitive automation
- webhook authentication failures for external systems
- quota breaches when workflow volume is growing
Send alerts to a channel monitored by the workflow owner. An alert channel that no one reads is the same as no alert.
Test alert delivery with a low-risk workflow or controlled failure before depending on alerts for customer-facing automation.
Retention Guidance
Keep detailed logs long enough to investigate customer-facing automation. If a workflow sends emails, creates invoices, changes records, or calls external apps, make sure the retention period covers the support window your team uses.
Shorter retention can be acceptable for low-risk internal reminders, but avoid reducing retention before a new workflow has run cleanly for a while.
Change Safely
After changing workflow limits, alerts, retention, or misfire policy, run or observe one low-risk workflow. Confirm alerts, logs, and run behavior match the new setting before relying on it for customer-facing automation.
Settings Review Checklist
Review workflow settings after adding many workflows, connecting new apps, changing schedules, or seeing repeated failures. Confirm limits, alert recipients, retention, and misfire policy still match the risk of the workflows currently running.