Automations Troubleshooting
Common issues encountered while configuring and operating Automations, along with their underlying cause and the recommended resolution. Ordered by the same sequence as the documentation, grouped by related topic.
warning
Every Dynamic Fields issue below traces back to one cause: a missing connector. Draw the connector first, and the field populates correctly.
Getting Started
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Submit button won't complete the Create Workflow dialog. | Title, Description, or Trigger Type is blank, or Date Range is half-set with only a Start or only an End date. | Fill in every required field completely, and either leave Date Range disabled or set both dates, before submitting. |
| Need to change a workflow's Trigger Type after creation. | Event-based versus Schedule-based is fixed permanently at creation time by design. | There is no edit path for this. Create a new workflow with the desired Trigger Type instead. |
Workflow Builder
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Can't find a delete icon on the Trigger node. | A workflow's own Trigger node cannot be deleted by design, only reconfigured. | Edit the Trigger node instead of trying to remove it. |
| A workflow is permanently gone after a cleanup pass. | Delete Workflow was used instead of switching the workflow off with the Status toggle. | None, deletion is irreversible. Use Status on the Details tab to pause a workflow reversibly instead. |
Event-Based Workflows
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Can't find a trigger for a specific CRM module in the picker. | The trigger catalog runs to 112 triggers across 12 pages, since every module contributes its own set. | Use the Module filter chips or the name search box in the Edit trigger Node panel instead of scrolling. |
Schedule-Based Workflows
| Symptom | Likely Cause | Resolution |
|---|---|---|
| A scheduled workflow doesn't fire during an expected week or month. | Date Range is enabled and the current date falls outside the Start Date to End Date window. | Check and either disable Date Range or widen the window. |
| A workflow saved as Daily at midnight runs at noon instead. | Opening the Custom Schedule tab after the schedule was already set recalculates the Cron Expression immediately, before any field on that tab is touched or Save is clicked. | Re-check the Current Schedule summary and Cron Expression right before clicking Save, every time Custom Schedule is opened, even just to look. If the expression shifted, reselect the correct preset or re-enter the correct values. |
Trigger Categories
| Symptom | Likely Cause | Resolution |
|---|---|---|
| A created Webhook doesn't appear as a Trigger option. | Webhook creation and that webhook's appearance in the Trigger catalog are separate steps. The connection was not confirmed automatic. | Verify directly in your own environment rather than assuming the webhook is already wired in. |
Action Categories
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Can't find SMS or WhatsApp actions under their own module name. | There is no separate SMS or WhatsApp module filter. | Filter by Messaging instead. SMS, WhatsApp, and generic conversation actions all live there. |
| "Open URL Edge By User ID" appears twice in the Edge Configuration action list. | A confirmed live duplicate entry, identical in name and description, and a known platform data quirk. | Either entry can be used. Treat it as a known issue rather than a configuration mistake. |
Condition Node
| Symptom | Likely Cause | Resolution |
|---|---|---|
| A rule meant to be excluded is still matching. | NOT was toggled on the wrong group. It applies per group, not per rule. | Wrap that specific rule in its own nested group, and toggle NOT there instead. |
| A Condition meant to check a numeric age or amount threshold keeps matching every record, aged or not. | The rule builder only offers string operators against a Formula field's output. There is no greater-than or numeric comparison available. | Use a Script node for a genuine numeric comparison, or treat the Condition as a presence check only ("is not empty") rather than a true threshold. |
Delay Node
| Symptom | Likely Cause | Resolution |
|---|---|---|
| A Delay node's Save fails, or the workflow errors at run time, with an "Invalid delay duration" message. | Confirmed in real executions: a Delay node's time fields resolved to a value the platform could not parse into a duration, for example an empty or non-numeric Dynamic Mention result. | Open the Delay node and check each field actually in use. Switch an uncertain field to list mode and enter a plain number directly, rather than relying on a Dynamic Mention whose source value isn't confirmed numeric. |
| A Dynamic Mention field on a Delay node doesn't show the expected upstream value. | This mode's actual available values were not verified live in testing. | Confirm directly in your environment, and fall back to typed-number (list) mode if uncertain. |
Formula Node
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Expecting a MAX or MIN formula function and it isn't in the list. | It does not exist in the live function picker, despite the Toolbox card's subtitle mentioning "max, min." | Use SUM for addition. There is no built-in MAX or MIN as of this verification. Use a Script node if min/max logic is required. |
Script Node
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Ctrl+Space on an empty line shows only generic JavaScript globals, no workflow fields. | Autocomplete matches on typed characters. An empty prompt has nothing to match against. | Type a few letters of the field's name first, for example casetype, then pick the suggested (nodeId.fieldName). |
| Unsure how later nodes reference the script's result by field name. | Response Mapping's schema was assumed to need a hand-pasted JSON sample. | Just save the node. JSON Input and the Schema Editor auto-populate from the script's own return statement. |
| Opening or saving a Script node fails with a 500 error, or the Monaco code editor never loads and the panel stays blank. | The Script node's editor loads the Monaco editor from a CDN dependency at runtime. A failed or slow load of that dependency leaves the editor area blank or causes the save request to fail. | Reload the page and reopen the node. If it recurs, check the browser console and network tab for a blocked or failed Monaco asset request, and confirm the CDN it loads from is reachable from your network. |
Dynamic Fields
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Condition node's Select field dropdown shows "No data" despite an upstream Trigger or Action existing on the canvas. | The Condition node is placed on the canvas but has no connector line drawn back to that upstream node. | Draw the connector from the upstream node's output handle to this node's input handle, then reopen Select field. Confirmed to populate correctly once connected. |
| Action node's Record ID field (Get Record By ID) won't save. The mention list is empty and typed values don't persist. | A select-only field with no typed-value fallback, on a node not yet connected to the upstream node holding the ID. | Connect the node to its upstream source first. Confirmed working once connected, for example selecting "Id (Current)" from a connected Trigger. |
| List node's Select List Data Field shows "No data" and "Field is required" even though an upstream Action returns an actual array. | The List node isn't connected to that Action. The array exists, but the node has no link back to it. | Connect the Action to the List node. Confirmed to then list and select the array field (for example "Get All Records... :data") correctly. |
| A Trigger-adjacent node (for example a Schedule-based Trigger's first Action) has no node to mention from at all. | Not a connection problem. A Schedule-based Trigger genuinely has no preceding node, so there is nothing for a dynamic mention to reference yet. | Use a saved filter built on the module's own list screen for select-only fields here (for example a Filter field), or a literal typed value for plain text fields. |
Automation Monitoring
| Symptom | Likely Cause | Resolution |
|---|---|---|
| A workflow's Trigger or Action node editor repeatedly comes back blank. | The node references a trigger or action ID the live catalog no longer recognizes. | Run Registry Health Check, find the workflow under Saved Workflows Health, expand the ERROR row for the exact broken reference, and reconfigure that node. |
Execution History
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Can't tell which step caused a FAILED execution. | Only the top-level Status and Error columns were checked. | Expand the row to view Step Logs. The per-node status (COMPLETED / SUCCESS / TRUE / FALSE / ERROR) isolates exactly where it broke. |
| Need the exact payload a node received, not just a pass/fail status. | Trying to diagnose from the Step Logs table alone. | Click Data on that step to open Workflow Log Details, toggle Raw JSON if needed, and Copy. |
Registry Health Check
| Symptom | Likely Cause | Resolution |
|---|---|---|
| The banner reads "Stale Registry Configurations Detected" despite Schema Warnings and Endpoint Errors both showing 0. | The staleness is at the individual saved-workflow level, from broken trigger or action references, not at the module or catalog level the four metric cards summarize. | Scroll to Saved Workflows Health and expand any row marked ERROR for the specific broken reference. |
| A module name from Registered Module Configurations doesn't match anything in the Action or Trigger Categories docs. | Internal module keys differ from the Designer's displayed category names, and at least one key has no confirmed mapped category. | Don't assume a direct name match. Investigate the module's actual contents in the live catalog instead. |
Permissions
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Toggling an Automations permission on a built-in role like System Owner has no effect. | Built-in roles open read-only in Edit Role. The panel shows no Save, Cancel, or Delete for them. | Create or use a role the organization created itself. Built-in roles can be reviewed but not edited from here. |
| A user with Manage System Workflow and Advanced Workflow Automation enabled still can't do something expected. | The exact capability boundary of each of the three Automations permissions was not confirmed live for every screen. | Test directly with a user scoped to exactly the permission in question, rather than assuming from the toggle's name. |
| A permission change doesn't take effect. | Cancel was clicked instead of Save, discarding the change. | After toggling a permission, click Save in the top right of Edit Role, not Cancel. |