Diagnosing and Resolving Common Flow Designer Issues for Top Misconfiguration Patterns - Support and Troubleshooting

Diagnosing and Resolving Common Flow Designer Issues for Top Misconfiguration Patterns .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .sn-kb { font-family: 'Source Sans Pro', -apple-system, BlinkMacSystemFont, 'Segoe UI', Arial, sans-serif; line-height: 1.6; color: #2C3E50; max-width: 1100px; } .sn-kb h1 { font-family: 'Gilroy-Bold', 'Source Sans Pro', sans-serif; font-size: 22px; font-weight: 700; color: #293E40; margin: 0 0 6px 0; letter-spacing: -0.3px; } .sn-kb .kb-meta { font-size: 12px; color: #6B7C85; margin-bottom: 20px; line-height: 1.8; } .sn-kb .kb-meta strong { color: #293E40; } .sn-kb h2 { font-family: 'Gilroy-Bold', 'Source Sans Pro', sans-serif; font-size: 15px; font-weight: 700; color: #fff; background: #293E40; padding: 8px 16px; border-radius: 6px; margin: 28px 0 14px 0; letter-spacing: 0.2px; } .sn-kb h3 { font-size: 13px; font-weight: 700; color: #293E40; margin: 20px 0 8px 0; padding-bottom: 4px; border-bottom: 2px solid #D5DFE1; } .sn-kb .err-block { background: #F4F6F7; border-left: 4px solid #D5DFE1; border-radius: 0 8px 8px 0; padding: 16px 20px; margin: 10px 0 16px 0; } .sn-kb .err-label { font-size: 10px; font-weight: 700; text-transform: uppercase; letter-spacing: 0.8px; color: #6B7C85; margin-bottom: 4px; } .sn-kb .err-msg { font-family: 'SF Mono', 'Cascadia Code', 'Consolas', monospace; font-size: 12px; color: #C0392B; background: #fff; padding: 6px 10px; border-radius: 4px; display: inline-block; border: 1px solid #D5DFE1; word-break: break-word; line-height: 1.5; max-width: 100%; } .sn-kb .detail-grid { margin: 10px 0; } .sn-kb .detail-item { font-size: 12px; margin-bottom: 6px; } .sn-kb .detail-item .label { font-size: 10px; font-weight: 700; text-transform: uppercase; letter-spacing: 0.6px; color: #6B7C85; display: inline; margin-right: 6px; } .sn-kb .badge { display: inline-block; padding: 2px 8px; border-radius: 10px; font-size: 11px; font-weight: 700; letter-spacing: 0.3px; white-space: nowrap; } .sn-kb .badge-error { background: #FDEDEC; color: #E74C3C; } .sn-kb .badge-warning { background: #FEF9E7; color: #E67E22; } .sn-kb .badge-ui { background: #EBF5FB; color: #2E86C1; } .sn-kb .badge-server { background: #EAFAF1; color: #1A5632; } .sn-kb .badge-ai { background: #F5EEF8; color: #8E44AD; } .sn-kb .symptom-text { font-size: 12px; color: #3B4A54; font-style: italic; } .sn-kb .ts-title { font-size: 13px; font-weight: 700; color: #293E40; margin: 12px 0 6px 0; } .sn-kb ol.ts-steps { margin: 0 0 10px 0; padding-left: 22px; font-size: 12px !important; line-height: 1.8; color: #3B4A54; } .sn-kb ol.ts-steps li { margin-bottom: 2px; font-size: 12px !important; } .sn-kb ol.ts-steps code { font-family: 'SF Mono', 'Cascadia Code', 'Consolas', monospace; font-size: 12px !important; background: #EBF5FB; padding: 1px 5px; border-radius: 3px; color: #293E40; } .sn-kb .kw-bar { font-size: 11px; color: #6B7C85; background: #EBF5FB; padding: 6px 10px; border-radius: 4px; margin-top: 10px; } .sn-kb .kw-bar strong { color: #2E86C1; font-weight: 700; } .sn-kb .source-tag { font-size: 9px; font-weight: 600; text-transform: uppercase; letter-spacing: 0.5px; color: #6B7C85; background: #F0F1F3; padding: 1px 6px; border-radius: 3px; margin-left: 6px; } .sn-kb .section-intro { font-size: 13px; color: #3B4A54; margin: 0 0 14px 0; } .sn-kb hr { border: none; border-top: 1px solid #D5DFE1; margin: 24px 0; } .sn-kb .related { background: #F4F6F7; border: 1px solid #D5DFE1; border-radius: 8px; padding: 14px 20px; margin-top: 24px; font-size: 12px; line-height: 1.8; } .sn-kb .related strong { display: block; font-size: 13px; margin-bottom: 4px; } .sn-kb a { color: #2E86C1; text-decoration: none; } .sn-kb a:hover { text-decoration: underline; } Product Area: Flow Designer Audience: Flow Designer administrators, platform developers Topic: Flow trigger issues, approval flow errors, subflow output, inline script errors, activation, ACL, email, plugins, scheduled flows, domain separation Applies to: Washington DC, Xanadu, Yokohama, Zurich, and later releases 1 Flow Not Triggering: Diagnosing and Fixing Trigger Condition Issues in Flow Designer The most common reasons a Flow Designer flow fails to trigger, with step-by-step diagnosis and resolution guidance.

Issue Flow Designer — Trigger Condition Flow never starts / trigger condition not working Visibility Flow Designer Severity Error Symptom A flow configured with trigger conditions never executes when a matching record is created or updated. No execution entries appear in the Execution Details log. Troubleshooting Step 1: Verify the trigger is active. Navigate to Flow Designer → open the flow → confirm Status = Active . A draft or inactive flow will never execute regardless of trigger conditions. Step 2: Check trigger condition logic. Open the Trigger section. Use Changes to (not just Changes ) when filtering for a specific value. Confirm the field referenced exists on the trigger table. Test using the Test button with a real record from the target table. Step 3: Check transaction timing. If the record is created by a business rule or script that runs in the same transaction as the event, the Flow trigger may not fire. Add a sys_id is not empty condition and test with a manual record update. Step 4: Review Flow Execution Logs. Navigate to Flow Designer → Execution Details. Filter by flow name. If no entries exist, the trigger never fired. If entries exist with errors, review the error message in the log. Step 5: Catalog item scope. For catalog flows, ensure the trigger is scoped to the specific Catalog Item sys_id. A table-level trigger on sc_req_item fires for all catalog items — add a condition: Catalog Item is [specific item] . Resolution Open Flow → Trigger section → use the Test button to evaluate the condition against a real record before activating. Confirm the exact field change event using sys_audit or the Flow Execution Log. For catalog items, always scope the trigger to the specific catalog item sys_id, not just the sc_req_item table. Check whether the business rule or process that creates/updates records runs before or after the trigger evaluates. Keywords: flow not triggering, flow never starts, trigger condition not working, Flow Designer, execution logs 2 Approval Flow Not Sending Email or Not Progressing Common causes of approval flows that fail to send notifications or stall indefinitely without progressing.

Approval Flow Not Sending Email or Not Progressing Issue Flow Designer — Ask for Approval Approval email not sent / approval flow stalls indefinitely Visibility Flow Designer Severity Error Symptom An approval flow runs without sending a notification email to the approver, or the approval record is created but the flow never advances past the approval step. Troubleshooting Check 1: Approver resolves to null. Open sys_approval after the flow runs. If Approver is empty, the approval action resolved a null group or user. Add a Log step before the approval step to print the resolved approver value. Check 2: Notification template is inactive. Navigate to System Notification → Notifications . Search for the approval notification used by your flow. Confirm Status = Active in the current instance (dev/test/prod — they may differ after a clone). Check 3: Approval group has no members. If the flow uses a group-based approval, navigate to sys_user_group and confirm the group has active members. An empty group creates an approval record that waits indefinitely with no notification. Check 4: 'Anyone Approves' vs 'Everyone Approves'. If set to Everyone Approves and one approver is inactive or departed, the approval never completes. Review the approver list for inactive users. Resolution Add a fallback approver : if the primary approver group is empty, route to a defined backup owner. Use the Set Values step before Ask for Approval to ensure the approver field is always populated before the approval step executes. Keywords: approval flow not sending email, approval not progressing, approver null, notification inactive, empty group, Everyone Approves, Anyone Approves 3 Subflow Output Variable Not Passed to Parent Flow Common causes of subflow output variables not being passed back to the parent flow correctly.

3.1 Subflow Output Variable Not Passed to Parent Flow Issue Flow Designer — Call Subflow Subflow output variable is null or missing in parent flow Visibility Flow Designer Severity Error Symptom A parent flow that calls a subflow receives null or empty values for the subflow's output variables, causing downstream steps to fail or behave unexpectedly. Troubleshooting Step 1: Check output mapping in parent flow. Open the parent flow → select the Call Subflow step → expand the Outputs section. Confirm each subflow output variable is explicitly mapped to a parent flow variable. If the Outputs section is empty, the return values are discarded. Step 2: Check subflow output in all branches. Open the subflow. If the output variable is only set inside an If or For Each block, it will be null when that block is not reached. Move the Set Output step outside the conditional, or add a default value assignment at the subflow's end. Step 3: Add a Log step for debugging. After the Call Subflow step, add a Log action: Subflow output: [output_variable_name] . Run the flow and check execution logs to confirm the value is populated before downstream steps consume it. Step 4: Verify subflow is published. An unpublished subflow may run a cached version that does not include the latest output variable definitions. Publish the subflow, then re-test the parent flow. Best Practice Always set a default value for output variables at the top of the subflow, then overwrite with the real value. This ensures the output is never null even if the main logic path is not reached. Resolution Open the parent flow → select the Call Subflow step → expand Outputs section → confirm all expected output variables are mapped to parent flow variables. In the subflow, ensure the output variable is set in all execution paths (both success and error branches). Add a Log step after the Call Subflow step in the parent flow to print the output variable value and confirm it is populated. Keywords: subflow output null, subflow variable not passed, Call Subflow, output mapping, parent flow variable, unpublished subflow 4 Script / Inline Script Errors and Null Pointer Exceptions Inline script errors are the fourth-largest support driver in Flow Designer. This section provides a checklist for writing null-safe scripts and diagnosing existing failures.

4.1 NullPointerException and Script Errors in Flow Designer Inline Scripts Issue Flow Designer — Inline Script NullPointerException / inline script error / undefined is not a function Visibility Flow Designer Severity Error Symptom A flow fails at an inline script step with a NullPointerException, undefined is not a function, or similar JavaScript error. The flow stops and does not progress to subsequent steps. Diagnosis: Find the Failing Line Open Flow Designer → Execution Details for the failing flow. Click the failed step. The error message shows the JavaScript line number. Cross-reference the line number with the inline script content to identify the exact failing statement. Troubleshooting Fix 1: Add null checks before field access. Never call methods directly on a field reference without checking for null first. Replace: var val = current.assignment_group.getDisplayValue(); With: var grp = current.assignment_group; var val = gs.nil(grp) ? '' : grp.getDisplayValue(); Fix 2: Validate GlideRecord queries. Always check .next() or .isValidRecord() before accessing fields: var gr = new GlideRecord('incident'); gr.get(sys_id); if (gr.isValidRecord()) { /* safe to read fields */ } Fix 3: Convert data pills safely. Data pills in inline scripts are objects, not strings. Use .toString() or String() when concatenating: var msg = 'Record: ' + String(fd_data.trigger.current.number); Resolution Test your inline script with a record that has all optional fields empty. If the script fails, add the missing null checks. Use the Script Debugger in the platform for interactive testing before deploying inline scripts in flows. Keywords: NullPointerException flow, inline script error, script fails flow designer, undefined is not a function, null check, GlideRecord, data pill 5 Flow Inactive or Not Published After Configuration The most common and fastest-to-resolve Flow Designer issue: a flow is configured correctly but not activated. This section explains activation, publishing, and post-clone activation steps.

5.1 Flow Inactive or Not Published After Configuration Issue Flow Designer — Activation Flow configured correctly but not running — status is Draft or Inactive Visibility Flow Designer Severity Warning Symptom A correctly configured flow never executes. The flow status shows Draft or Inactive. This is the most common post-clone and post-deployment issue. Troubleshooting Step 1: Check flow status. Open Flow Designer → locate your flow → check the status badge in the top right corner. Draft = will not run. Active = running. Click Activate to enable. Step 2: Post-clone activation. After cloning an instance, all flows arrive in their source state. If the source was inactive, they will be inactive in the target. Navigate to Flow Designer → use the Status filter to find all inactive flows → activate those that should be running. Step 3: Protected flows. If the Activate button is greyed out, the flow may be protected by its update set or application scope. Navigate to sys_hub_flow → find the record → check the Protection policy field. Set to None to allow editing, then activate. Step 4: Verify in Execution Logs. After activating, trigger the flow manually by running a test record through the trigger condition. Navigate to Execution Details and confirm a log entry appears. If no entry appears, the trigger condition is not being met — see KB: Flow Not Triggering. Resolution Open the flow in Flow Designer → check the Status indicator at the top right. If it shows Draft or Inactive , click Activate . After a clone, navigate to Flow Designer → filter by Status = Inactive → bulk-activate all flows that should be running. If the Activate button is greyed out, check the application scope protection setting on the flow record in the sys_hub_flow table. Keywords: flow inactive, flow not published, flow draft, activate flow, post-clone activation, protection policy, sys_hub_flow 6 Role or ACL Blocking Flow Execution Flow execution failures caused by missing roles or ACL restrictions are often silent — the flow stops with a vague security error. This section explains how to identify and fix them.

6.1 Role or ACL Blocking Flow Execution Issue Flow Designer — ACL / Security Flow fails silently or throws vague security error — missing role or ACL restriction Visibility Flow Designer Severity Error Symptom A flow stops at a read or write step with a vague security or access denied error. The flow works for admin users but fails for end users or service accounts. Troubleshooting Step 1: Find the failing step. Open Execution Details for the failed flow run. Identify the step that generated the security error. Note the table it was reading or writing. Step 2: Identify the required role. Navigate to sys_security_acl . Search for ACLs on the table identified in Step 1 with Operation = read or write . Note the required role(s). Step 3: Check triggering user's roles. Identify who triggered the flow from Execution Logs. Navigate to that user's profile → Roles tab. Confirm they have the required role. If not, grant the role or reconfigure the flow. Step 4: Use 'Run as' for elevated steps. If a specific step requires elevated access, configure the action to Run as: System Account rather than granting broad roles to end users. This is the preferred pattern for write operations on restricted tables. Step 5: Test with impersonation. In dev, use System → Impersonate User to run as the affected user. Attempt to trigger the flow. If it fails, you have confirmed the role gap. Grant the role, then re-test. Resolution Identify which table step is failing from the Execution Log error. Navigate to that table's ACL ( sys_security_acl ) and identify the required role. Grant the triggering user or service account the required role — or configure Run as: System on the specific flow action that needs elevated access. Use Impersonate User in dev to reproduce the failure and confirm the fix. Keywords: ACL blocking flow, role missing flow, security error flow, Run as System, impersonate user, sys_security_acl, flow access denied 7 Notification / Email Action Not Sending When a flow's Send Email or Send Notification step runs without error but no email is received, the issue is almost always instance-level email configuration, not the flow itself.

7.1 Notification or Email Action Not Sending Issue Flow Designer — Send Notification Flow Send Email / Send Notification step completes but no email is received Visibility Flow Designer Severity Warning Symptom The flow completes without error but the intended recipient never receives the email. The step shows as completed in Execution Details with no failure. Troubleshooting Check 1: Outbound email service status. Navigate to System Mailboxes → Outbound → confirm the outbound mail configuration is Active. Check System Properties for glide.email.smtp.active = true . Check 2: Instance not in demo/debug mode. Navigate to System Diagnostics → Stats . Check whether Email sending is disabled for demo is set. This silently captures emails without delivering them. Check 3: Notification template is active. Open the notification template referenced in your flow's Send Notification step. Confirm Active = true in the current instance. Templates may be inactive after a clone from dev. Check 4: Recipient field resolves to a valid email. Add a Log step before the Send Email step. Log the recipient value. Confirm it is a valid email address and not null or a sys_id. Check 5: SMTP relay health. If emails are queued but not delivered, the issue may be upstream of ServiceNow. Work with your email administrator to check SMTP relay logs for delivery failures. Resolution Navigate to System Mailboxes → Outbound → confirm Status = Active and SMTP settings are correct. Check System Properties → glide.email.smtp.active = true . Confirm the instance is not in debug/demo mode: System Diagnostics → check Email sending disabled for demo . Verify the notification template referenced in the flow action is Active in this instance. Test by sending a manual notification from System Notification → Test . Keywords: email not sending, notification not delivered, glide.email.smtp.active, demo mode email, SMTP flow, Send Notification, outbound mailbox 8 Update Set or Plugin Version Mismatch Breaking Flows Flow Designer breakages after upgrades or update set promotions are almost always caused by plugin version mismatches or unresolved update set conflicts on flow-related records.

8.1 Update Set or Plugin Version Mismatch Breaking Flows Issue Flow Designer — Plugin / Update Set Flows break after upgrade or update set promotion — plugin version mismatch Visibility Flow Designer Severity Error Symptom Flows that worked before an upgrade or update set promotion fail to load, activate, or execute. Flow Designer may show blank canvases or missing action types. Troubleshooting Fix 1: Update all Flow Designer plugins. Navigate to System Applications → Plugins . Search for and update: (1) Flow Designer, (2) Workflow Studio, (3) Unified Developer Core. All three must be on compatible, up-to-date versions. Repair each plugin after updating. Fix 2: Run Update Set Preview before promoting. Before promoting an update set containing flows or subflows, run Update Set Preview . Look for conflicts on sys_hub_flow , sys_hub_action_type , and sys_hub_subflow records. Resolve conflicts before completing the promotion. Fix 3: Verify spoke versions match across environments. If your flow uses Integration Hub spokes, confirm the spoke version is identical in source and target. Promote spokes first, then flows that depend on them. Fix 4: Repair Flow Designer after upgrade. After any platform upgrade, navigate to Plugins → Flow Designer → click Repair . This re-registers extension points and resolves version drift. Prevention Before every upgrade, document the current Flow Designer, Workflow Studio, and Unified Developer Core plugin versions. After upgrade, verify all three updated together. Add this to your upgrade runbook. Resolution For plugin issues: navigate to System Applications → Plugins → search for Flow Designer , Workflow Studio , Unified Developer Core → confirm all are on the same latest version → update if needed. For update set conflicts: before promoting, use Update Set Preview to identify conflicts on flow-related records. Resolve spoke version conflicts by ensuring the target environment has the same spoke version as the source. After any upgrade, run the Flow Designer plugin repair: Plugins → Flow Designer → Repair . Keywords: plugin version mismatch, update set conflict, Flow Designer upgrade, Workflow Studio, Unified Developer Core, spoke version, repair plugin 9 Scheduled Flow Not Running at Expected Time Scheduled flow failures are usually caused by one of three issues: Flow Engine job backlog, timezone misconfiguration, or a Wait step blocking all future runs.

9.1 Scheduled Flow Not Running at Expected Time Issue Flow Designer — Schedule Scheduled flow does not run at the configured time or skips executions Visibility Flow Designer Severity Error Symptom A scheduled flow does not execute at its configured time. No entry appears in Execution Details, or the flow fires at the wrong time, or runs are skipped entirely. Troubleshooting Check 1: Flow Engine Event Handler health. Navigate to System Scheduler → Scheduled Jobs → search for Flow Engine Event Handler . Confirm Next Action is a future timestamp. If it shows a past date, the job is stuck. Click Execute Now to restart it. Check 2: Timezone alignment. Open the flow's schedule definition. Confirm the timezone matches the intended run timezone. ServiceNow schedules use the instance timezone by default — if your users expect local time, set the timezone explicitly. Check 3: Wait step blocking execution. Open Execution Details . If a previous execution of the scheduled flow is still in a Waiting state, it may block new executions. Navigate to sys_flow_context → filter by flow name and state = Executing → cancel any stuck contexts. Check 4: Duration units. If using Wait for Duration , confirm the value is in the correct unit. '60 minutes' vs '60 seconds' is a common mistake. Review the step configuration carefully. Resolution Navigate to Scheduled Script Executions → search for Flow Engine Event Handler → confirm Next Action is a future date/time. If past-dated, update Next Action to now and run. Check the flow schedule's timezone setting — confirm it matches the user's expected local time. For Wait for Condition timeouts, set a maximum wait duration in the flow step to prevent indefinite blocking. If using Wait for Duration , confirm the duration input is in the correct unit (seconds vs. minutes). Keywords: scheduled flow not running, flow not firing on schedule, Flow Engine Event Handler, timezone flow, Wait for Duration, sys_flow_context, stuck flow 10 Domain Separation Causing Flow Visibility or Execution Failures Domain separation introduces visibility constraints that affect which flows and subflows execute in a given tenant context. This section explains the most common domain-related flow failures and how to resolve them.

10.1 Domain Separation Causing Flow Visibility or Execution Failures Issue Flow Designer — Domain Separation Flow not visible or not executing in expected tenant context — domain separation constraint Visibility Flow Designer Severity Error Symptom A flow that exists in the system is not visible or does not execute for users in a specific domain. Subflows called from a global flow fail because the subflow is in a restricted domain context. Troubleshooting Check 1: Flow domain assignment. Navigate to sys_hub_flow . Open the flow record. Check the Domain field. For flows that should run across all tenants, set Domain = Global . Subdomain-scoped flows are only visible in that domain's context. Check 2: Duplicate flow records across domains. Search sys_hub_flow for flows with the same name. If duplicates exist in multiple domains, the subdomain version shadows the global version. Remove or merge duplicates, keeping the version that should take precedence. Check 3: Subflow domain context. A parent flow in Global calling a subflow in a subdomain may fail if domain visibility restricts the subflow from being found. Ensure subflows are scoped to the same or a higher domain than their callers. Check 4: Post-clone domain drift. After cloning, domain assignments on flow records may change. Audit sys_hub_flow after a clone to confirm domain assignments match expectations in the target instance. Best Practice In multi-tenant deployments, maintain a flow domain inventory document. Before adding a new flow, explicitly decide: Global (all tenants) or domain-scoped (specific tenant only). Document the decision for each flow. Resolution Navigate to sys_hub_flow → open the flow record → confirm the Domain field is set to Global for flows intended to run across all tenants. Check sys_hub_flow for duplicate flow records with the same name in different domains — subdomain versions shadow global versions and may be misconfigured. For subflows, ensure the subflow is in the same or higher domain as the calling flow. Use Domain override carefully — document which flows have subdomain overrides to prevent maintenance confusion. Keywords: domain separation flow, flow not visible domain, subdomain flow, global domain flow, sys_hub_flow domain, post-clone domain drift, multi-tenant flow