Scheduled Flow Trigger

[Tarun Kumar10]

Hello everyone, I'm looking for some clarity on how ServiceNow handles ownership of scheduled flow triggers.

When a user configures a flow that runs on a schedule, the trigger appears to be associated with the user who created it, rather than using the "Run As" user or any other property defined in the flow. In our case, the person who originally configured the flow has since left the company, but the trigger still shows their name. Despite this, the flow continues to run without any issues.

My questions are:

• Why does ServiceNow retain the original user's name in the trigger?
• What is the recommended best practice for handling such scenarios, especially when the original user is no longer active?
• Is there any official documentation or guidance from ServiceNow on how to manage or reassign ownership of these triggers?

I've searched the documentation and community forums but haven't found anything definitive so far. I’d appreciate any insights or recommendations from others who have dealt with this.

Thanks in advance.

[Maik Skoddow]

Hi @Tarun Kumar10 

yes, I can confirm the lack of clearance regarding that topic. I had a similar issue and digged deeper into that topic. As a result, I wrote an article about it: Do not run into that weird Flow Designer bug, Part 2

Maybe it helps.

[Tarun Kumar10]

Hi @Maik Skoddow , Thank you so much for your response and for sharing the sharing the KB, just a question since the user is inactive but there's no impact on the flow, are there any best practices you'd recommend for handling such scenarios? 

[Maik Skoddow]

Hi @Tarun Kumar10 

no, I don't have any special recommendations. If a user is deactivated ServiceNow will not check where the user is referenced and which impacts on running jobs / flows / whatever this deactivation has. So its your responsibility to validate before and raise warnings accordingly.

Maik