Subject: OOB Incident Workflows Missing in Yokohama Instance

CHANTIE
Tera Contributor

Thursday

Subject: OOB Incident Workflows Missing in Yokohama Instance

Hi all,

I’m unable to find the out-of-the-box workflows for the Incident table in Workflow Studio or the Workflow Editor in our Yokohama instance.

I’ve already verified the following:


• Checked the wf_workflow table for records related to the Incident table — none found.

• Verified that I’m in the global scope and have admin access.

.Loaded demo data from workflow authoring tool

Interestingly, these OOB Incident workflows are visible in the Xanadu instance, but not in Yokohama. I also checked with the ServiceNow AI bot, which mentioned that no OOB workflows were removed in the Yokohama release.

Could you please confirm if this could be related to missing demo data or if there’s a plugin/configuration needed to bring back the OOB workflows for the Incident table?

 

These are the only flows that i can see in workflow studio related to incident

Preview file
5020 KB
0 Helpfuls
  • 347 Views
6 REPLIES 6

Connectmustaq
Mega Guru

Thursday

Hi @CHANTIE ,
Your Yokohama instance not showing out-of-the-box (OOB) Incident workflows is expected behavior — it is not due to missing demo data or a plugin issue. Starting with the Yokohama release, ServiceNow fully transitioned Incident Management automations from legacy Workflow Editor workflows to Flow Designer–based flows in Workflow Studio.
Here’s what’s happening and how you can verify or restore expected behavior:
Why OOB Workflows Are Missing
  • Yokohama deprecated classic Workflow Editor workflows (records from the wf_workflow table) for major ITSM modules, including Incident, Change, and SLA workflows.​​
  • All OOB automation has been reimplemented as Flow Designer flows (subflows, playbooks, and flow templates) managed in Workflow Studio.
  • This transition means you won’t see classic workflow records (like “Incident - Create Task”, “Incident Lifecycle”, etc.) in wf_workflow or Workflow Editor anymore — they simply no longer ship with the release.​
How to Verify in Yokohama
  1. Navigate to Workflow Studio → Flows.
    Search for “Incident” — you should find:
    • “Incident - Create Major Incident Flow”
    • “Incident - Create Problem Flow”
    • “Incident - Assignment Rules Flow”
    • “Incident - Auto Closure Flow”
  2. Enable relevant Flow Designer plugins if not already active:
    • “Flow Designer” (com.glide.hub.flow_base)
    • “Process Automation Core” (com.snc.process_automation)
    • “Incident Management - Flow Designer Support” (com.snc.incident.fd_support)
  3. Check the “Flow Designer Runtime” plugin if any flows are not executing as expected.
If You Specifically Need Legacy Workflows
  • The legacy Incident workflows are no longer shipped in Yokohama. However, if you must replicate that model for backward compatibility, you can:
    • Import wf_workflow XMLs from an earlier (e.g., Xanadu) instance.
    • Clone or manually copy them into your Yokohama instance (not recommended for long-term support).
    • Note: These workflows will not automatically integrate with new Incident flow triggers or playbooks in Yokohama.​
The absence of OOB Incident workflows in your Yokohama instance is aligned with the platform’s modernization strategy:
  • No plugin or demo data will restore them, since OOB Incident automation is now implemented as flows/subflows.
  • Focus on Flow Designer and Workflow Studio to view, modify, or extend Incident processes.
If your instance doesn’t list the “Incident – Create” or similar Flow Designer items, verify that the Incident Management - Flow Designer Support plugin is active — that’s now the entry point for the OOB Incident flows.
 
you may find below thread helpful:
 
please mark the answer as correct and helpful based on the impact!!
 
Kind Regards,
Shaik Mohammed Mustaq

CHANTIE
Tera Contributor
In response to Connectmustaq

Friday

Tq but i am not able see incident table related flows in workflow studio ass well after checking all plug-ins. You can see the image i provided above, i can see those workflow only in flow studio

0 Helpfuls

Connectmustaq
Mega Guru
In response to CHANTIE

Friday

Hi @CHANTIE ,

 

In the Yokohama release, what you’re seeing is expected behavior: Incident-related automations now exist only as Flows (in Flow Designer) and not as Workflows within Workflow Studio—even though both tools coexist under the “Workflow” umbrella in documentation. The key reason is that Workflow Studio in Yokohama has been redesigned to manage Flow Designer assets (flows, subflows, actions, playbooks, and triggers) rather than legacy wf_workflow-based records.​

Why Incident Flows Do Not Appear in Workflow Studio

  • Workflow Studio in Yokohama shows Flow Designer items, not legacy Workflow Editor definitions.

  • The Incident Management automations—like Create, Reopen, Resolve, and Major Incident creation—were all migrated to record-triggered Flows under the Flow Designer engine.

  • What once appeared as “Incident - Create” or “Incident - Close” workflows in Workflow Editor or wf_workflow table are now replaced by Flows visible only under Flow Designer → Flows.

  • Therefore, you will see them in Flow Designer (your screenshot reflects this correctly), but not under Workflow Studio, even with all relevant plugins active.​

Confirming This Transition

To confirm your instance is configured correctly:

  1. Navigate to Process Automation → Workflow Studio → Triggers to verify active triggers exist for record-based Incident flows.

  2. Open any Incident record, right-click the column header → Configure → Flow Designer Flows to view flows associated with the table.​

  3. The triggered flows should list under the Flow Designer interface, launched automatically when you click them.

How to View Incident Flows in Workflow Studio

If you want to visualize your Incident-related automations inside Workflow Studio:

  • Workflow Studio (v26.2 and higher in Yokohama) allows you to “import Flow Designer assets” for orchestration or cross-flow analysis, but it doesn’t replicate legacy workflow diagrams.

  • You can select New → Flow / Subflow / Trigger from the Workflow Studio interface and link it to existing record-triggered flows under “Incident” to manage from one workspace.​​

In Summary

  • Workflow Editor (legacy): Deprecated; no more Incident workflows there.

  • Flow Designer: Where all Incident automations now reside.

  • Workflow Studio (Yokohama): A consolidated visual shell for Flow Designer assets (Flows, Subflows, Actions, Playbooks)—not the old wf_workflow items.

Your instance setup is correct. There’s no missing plugin — it’s simply how ServiceNow Yokohama merges automation under Flow Designer and Workflow Studio as a unified low-code environment.

 

You may find below thread helpful:

Please mark the answer as correct and helpful based on the impact!!

 

Kind Regards,

Shaik Mohammed Mustaq

OxDhanush
Tera Contributor
In response to Connectmustaq

Saturday

  1. in step this step Navigate to Process Automation → Workflow Studio → Triggers to verify active triggers exist for record-based Incident

    i see zero triggers

    OxDhanush_0-1761411280016.png

     

  2. in step 2 

    Open any Incident record, right-click the column header → Configure → Flow
    not able to see Flow after configure.

    Anyway thanks for all the help.
0 Helpfuls