Subject: OOB Incident Workflows Missing in Yokohama Instance

[CHANTIE]

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

[Connectmustaq]

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:

• https://www.servicenow.com/docs/bundle/yokohama-release-notes/page/release-notes/summary/rn-summary-...

• https://www.servicenow.com/docs/bundle/yokohama-release-notes/page/release-notes/it-service-manageme...

 

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

 

Kind Regards,

Shaik Mohammed Mustaq

[Ankur Bawiskar]

@CHANTIE 

which OOTB workflows on incident you are referring?

the screenshot you shared is for Flow and not Workflow