I created a flow which has some API keys. Once done, I moved the app with the keys to a new space.
Now the automation fails,
[400] app_no_permission: [AppNoPermissionException] Actor with id 281887 and type WORKFLOW_DEF has invalid permission to access app 64003!
How to fix this? Can’t we change app workspace after building a flow?
Humor me and open the automation, then save it and try again. I think I ran into this 1x in the past.
I opened the flow from the Tape account owner and saved it. Now it works.
Basically, I just had to re-pick the moved app in the search app brick of the flow.
Do you know if our automations are tied to a specific user or space?
I’m wondering if we build an automation and connect three apps from different workspaces, and then later reorganize those apps into other workspaces, will the flow break?
You should be able to move apps around with out it breaking to an extent.
Workflow permissions are based on the permissions of the user that last saved the workflow at that given time.
So for example if I was the last person to save an automation and at that time i didn’t have the correct permission and then you gave me the relevant permissions to an app that would not work until I modified a the automation and resaved again.
Now there is a way to set the API key used in an automation what I am not sure about (and maybe i should try) is if that key only takes affect for the script block it is set in or for the whole automation.
The whole save and permissions process was explained to me once I think by @Leo and i am sure it was a much better explanation than i have just given.
Anyway if I have not made sense let me know and I will try again 
It makes sense. Basically if I move around app, as a best practice, try to resave everything.
Known issues/situations are less scarier than unknown ones. This one can now be handled.
Thanks again Jason for explaining it so clearly 
- and yes, Taha, you’re absolutely right in how you understood it.
Just to confirm: Automations always run with the permissions of the last user who saved them. This is important for scenarios like when a partner sets up automations for a client, and later leaves the workspace or gets downgraded - we don’t want those automations to break just because of that.
This also affects cases where you create a brand new workspace or app, and try to immediately use it in an automation. If you don’t resave the automation after gaining the right permissions, it might fail. I’ve been caught by that myself before 
In the future, we plan to improve this with a smarter system: newly gained permissions would automatically apply to automations, but any lost permissions would only apply after the automation is saved again. That would be the ideal behavior and is already part of our roadmap. But right now, other features are a bit higher priority – so we’re still using the current model, which is exactly what Jason described.
Let us know if anything’s unclear, always happy to help!
Best,
Leo