Issue with Workday Integration

User390050
Tera Contributor

‎02-02-2025 02:55 PM

Having issues with Workday Integration. I have followed the steps listed in the document below:
https://www.servicenow.com/docs/bundle/vancouver-integrate-applications/page/administer/integrationh...

When i go ahead and run the Run Workday Integration Flow from Flow Designer, I get error below: "Flow was not executed as the Workday Service was already running". Workday team has verified that there's no other job running. What could be the root cause of this?

User390050_0-1738536819407.png

User390050_1-1738536874788.png

 

0 Helpfuls
  • 2,033 Views
4 REPLIES 4

AadithyaM
Tera Contributor

‎02-17-2025 01:05 PM

This error in ServiceNow typically occurs when there's a mismatch between the actual state of Workday integration and what ServiceNow believes to be the state. Here are the potential root causes

  1. Stuck Integration State - ServiceNow might have a "locked" or "running" state stored in its system, even though no actual integration is running This can happen if a previous integration job ended abnormally without properly clearing the state
  1. Cached Status -ServiceNow might be caching an outdated status of the Workday integration ,The status might not have been properly updated after a previous run.
0 Helpfuls

User390050
Tera Contributor
In response to AadithyaM

‎02-18-2025 02:26 PM

Thanks for the reply @AadithyaM. I checked the current executions for the "Run Workday Integration Flow" but didn't see any active as all of them say Complete. I also tried to clean the cache but going to cache.do and clicking "clear cache". Re-ran the flow and same issue. Are there any troubleshooting steps I can take? 

0 Helpfuls

AadithyaM
Tera Contributor

‎02-17-2025 01:11 PM

This error in ServiceNow typically occurs when there's a mismatch between the actual state of Workday integration and what ServiceNow believes to be the state. Here are the potential root causes.

  1. Stuck Integration State

  ServiceNow might have a "locked" or "running" state stored in its system, even though no actual integration is running.This can happen if a previous integration job ended abnormally without properly clearing the state

2.Cached Status

ServiceNow might be caching an outdated status of the Workday integration

The status might not have been properly updated after a previous run

 

0 Helpfuls

AadithyaM
Tera Contributor

‎02-17-2025 01:13 PM

This error in ServiceNow typically occurs when there's a mismatch between the actual state of Workday integration and what ServiceNow believes to be the state. Here are the potential root causes.

  1. Stuck Integration State

  ServiceNow might have a "locked" or "running" state stored in its system, even though no actual integration is running. This can happen if a previous integration job ended abnormally without properly clearing the state 2.Cached Status -ServiceNow might be caching an outdated status of the Workday integration,The status might not have been properly updated after a previous run.

0 Helpfuls