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?

[Vishnu_Srinivas]

@andresalesc  Thank you,

This resolved the issue for me. when I resolved the child subflow and then return to parent subflow and try to save it got saved with no errors

[denmanty]

Having the same issue, although I can save the action fine. I get the error on the logs and I am impersonating a user. Running the subflow as system.
Has anyone found how to resolve this?

[denmanty]

Tried as admin also and still get the error

[Bsublett]

I am seeing the same error. Has anyone figured out a fix yet?

[haninger_3]

I experienced this issue after moving a flow and subflows from one sub-prod instance to another. I seem to have been able to resolve it, but I don't feel totally confident yet, since Flow is so flakey. Time will tell....

I was trying to move the flows from my Test (source) instance to Dev (target)

Dev has a newer version of WF Studio than Test, though I don't think this matters

When I got this error, I copied the sys_id from the little error bubble and then searched for it in the "source" sub-prod instance using the (excellent) SN Utils slash command /sysid <sys_id>     (HIGHLY recommend this tool! @Arnoud Kooi  hope you're able to work on this tool on company time)

This told me the record that was causing trouble.

Looking up the same record in the target instance showed that it could not be found.

I probably could have just exported the record from the source instance as XML (along with its related lists) but would prefer to do this in an update set in a more "official" way.

Again in the source instance, I opened a new update set.

In WF Studio, I found the action that was "missing" from the target instance and edited its name, saved, and published, so it would be captured in my update set.

I only edited the name so that there would be some change that would let me save and publish so that the action would be captured in my update set. If you wanted, you could also try adding or editing a step in the action or flow or subflow.

Moving the update set from the source instance to the target instance seems to have resolved the issue.

(Edit: Forgot to mention that when previewing my update sets, every update errored and I had to accept the remote update in order to commit the update set. The "mistake" I made when initially moving my update set into our Dev instance was that I skipped these errors when I should have accepted them. Now I know!)

Good luck!