Skip to content

Troubleshooting Workflows ​

Last updated

Debugging approach ​

  1. Open the workflow's History and click the latest run. A red box shows the error; the Step Log shows which node types ran and which one has ✗.
  2. The Step Log shows a Log node's message and a short summary of other nodes' outputs, but not variable values on their own. Add a Log node such as Value is {{yourVariable}} to see one.
  3. Each History row and the run's Trigger: line show what started the run (Run now, Tag change, Schedule and so on).

Symptoms and fixes ​

SymptomCauseFix
Nothing happens when the tag changesThe workflow is Disabled (new workflows are)Turn on the toolbar toggle so it reads Enabled
Nothing happens, workflow enabledChanges not saved; the trigger has no Tag Path; the tag's device is offline; the value is inside the deadbandSave; pick the tag with the browse button; check the tag's live value on the Tags page
Run fails: No trigger node found in workflowThe workflow has no trigger nodeAdd a Manual or Called by Workflow trigger
Run fails: Workflow is emptyNo nodes savedAdd nodes and Save
Clicking or dragging from the palette does nothing visibleNew nodes appear at the same spot near the top-left, often under earlier onesClick once, then drag the new node away
A wire from Value/Result into the next node doesn't pass the valueThe source node didn't run earlier in the same path (a sibling branch, or not reached yet)Wire from a node upstream on the same path, or use its Output variable and {{name}}
Nodes after Connected/Disconnected of Network Event don't run on Run NowRun Now has no network state, so neither branch is takenTest by making the Check URL reachable or unreachable
Branch 3 of a Fork never runsNumber of branches is 2Set it to 3
Email or tag shows a literal {{temp}}No variable or trigger key with that name at that point in the run, or a dotted nameCheck spelling and case; make sure the node that sets it runs first; avoid {{a.b}}
Email body arrives with quotes around it, or an Expression returns nothingText or code typed inside double quotes, the old JSON-box form, e.g. "return vars.x;"Remove the outer double quotes
Expression error: …A JavaScript error in the codeFix the code; test with fixed values
Headers are not valid JSON / Headers must be a JSON objectHeaders (JSON) isn't a JSON object (the box shows Not valid JSON)Type an object such as {"X-Api-Key": "abc"}
Neither SMTP nor Resend API is configuredNo SMTP host, and no relay credentials on this applianceConfigure SMTP Email
Relay timeoutNo SMTP host, and the Scada.Ink relay could not be reachedConfigure SMTP Email, or give the appliance internet access
SMTP timeoutServer unreachable or not answering, or the wrong portCheck host, port and firewall; try Send test email in Settings
… rejected by SMTP server: <code> <reason>The server refused the login, sender, recipient or messageFix what the reason names; see Email (SMTP) Settings
Write access not enabled for device 7Set Tag to a device without write accessTurn on Tag Write Access for the device
Source tag 3:Line1/Count has no value to copyThe source tag has no value yetCheck the source device is connected
Write not enabled for MQTT device 4 / MQTT device 4 not foundMQTT device without write access, or not an MQTT deviceEnable write, or pick the MQTT device
No column values to insert / …updateWrite DB's Column values list is emptyAdd a name and value for each column to write
Unknown column in table "…": …A Column values name doesn't match the tableCopy the exact column name from the Data Tables page
Table not found: …Table name doesn't match the Data Tables pageCopy the exact name
Invalid JSON: …Decode JSON got text that isn't JSONCheck the source variable
TCP timeout / connect ECONNREFUSEDHost or port wrong, device not listeningCheck address and port; test with the device's own tool
Maximum workflow nesting depth reached (5)Workflows or scripts calling each other in a cycleBreak the cycle
Cannot call self recursivelyRun Workflow points at its own workflowUse a Loop, or a separate workflow
No script ID configured / No workflow ID configured / No ladder task configuredPicker left emptyChoose the target
Workflow execution limit reached (>1000 steps)Almost always a wire looped back to an earlier node; occasionally a genuinely very large workflowFind and remove the loop; if the workflow really is that large, split it into called workflows
Hundreds of runs a minuteTag Value on a changing tag (level-based), or Tag Change on a noisy analogTrigger on a one-shot bit; see How Workflows Run
A disabled workflow still runsAn editor or administrator used Run Now, in the editor or from a buttonExpected — Run Now can test a disabled workflow
Workflow "…" is disabledA schedule, script, pipeline, Run Workflow node or operator's button started a disabled workflowEnable the workflow
Workflow "…" is already runningIt was started again before its last run finished; the new run was skippedShorten the run, or trigger less often. See How Workflows Run
Jump To: no node is labeled "…"No node's Node Label matches, or two nodes share itSet a unique Node Label on the target
Shutdown trigger didn't finish its workShutdown runs get about 2 s before the service stopsKeep Shutdown workflows short
A run shows failed with Interrupted: the appliance restarted during this runThe service restarted while it was runningRun it again if it matters
Reformat Date/Time: "…" is not a dateThe value isn't a date the node can readPass an ISO date or a Unix time
Retentive Timer reaches Done far too earlyIt measures time between runs, not time the condition was trueUse an RTO in ladder logic
Count Up (not retentive) never reaches the presetThe count resets every runTick Retentive (persist across runs)

See also ​

Scada.Ink Help Center