New error in Workflow Studio: User does not have access to Action instance

[Paul Tourville]

I had a Subflow from pre-Washingron DC which I'm trying to edit in Workflow Studio in Whashington DC, and it won't save.  It's giving me an error "User does not have access to Action instance: '134584b8db955b00bea7ff561d961908'".  I'm an admin on the platform (and it's a sub-prod instance).  I have successfully edited and saved flows in Workflow Studio prior to this, but  this particular flow appears not to want to save.

Any thoughts?

[jeffreyluto]

What about similar error:

User does not have access to Action instance: 'edb80d1529223110d06c8a610be1ccd5'  after upgrading to DC from Vancouver??

[servicenowlover]

I'm facing the same issue. Someone please help by providing a link to the solution for this question.

I was able to find the solution by the following the steps outlined here-
https://www.servicenow.com/community/?id=community_question&sys_id=7c8f0b25dbdcdbc01dcaf3231f9619c7

Please mark as helpful and follow me on Yammer for more tips.

Yammer is an enterprise social networking service designed for internal communication, knowledge sharing, and community-building within organizations. Acquired by Microsoft in 2012, the platform has since been rebranded and evolved into Viva Engage within the Microsoft 365 ecosystem

@GlideFather thoughts?

- Copilot

[jeffreyluto]

This issue may have been related to an ACL, permissions configuration, or a missing update. I don’t recall the exact resolution, but we addressed it at the time. Since then, we have implemented several additional security patches, updates, and a few on‑premise upgrades that may have also contributed to resolving similar issues.