Moving an app to a different workspace kills automation

🔧 Bugs & Issues
1

Hi,
I moved my “Prompt Database App” from a closed workspace to an open workspace. My user has access for both. However - I wondered why I started getting this issue:

[16:47:06.524] Action execution failed with error:
[400] app_no_permission: [AppNoPermissionException] Actor with id 280777 and type WORKFLOW_DEF has invalid permission to access app 58932!

I needed to save the automation again, but I think I shouldn’t have to. I just moved the app into a different place where my automation still has access to.

1 Like
2

Yes it does. You’ll have to open the automation and save it again just so permissions can be re-established!

Been there and done that. Probably there might even be a post I made.

3

Yes, but I think thats a bug. I shouldn’t be required to “reestablish” the connection manually. I just move the app, it should reestablish itself or let me know, if the automation brakes proactively, when there is a reason for this. E.g. another user created an automation and I move the app to a place, where this user has no access:

+------------------------------+----------------------------------+
|           Action             |             Behavior             |
+------------------------------+----------------------------------+
| User 1 moves App             |                                  |
| from workspace A to B        |                                  |
+------------------------------+----------------------------------+
| Automation X Owner (User 2)  | Automation should NOT break      |
| has access to A and B        |                                  |
+------------------------------+----------------------------------+
| Automation X Owner (User 2)  | Move should notify User 1 that   |
| has access to A but not to B | Automation X will break          |
+------------------------------+----------------------------------+
1 Like
4

In my scenario I was User 1 and 2 in person.

5

Yup, I understand.

Here’s the response from Leo, at the time when I had raised the ticket.

1 Like
6

OK, lets leave this ticket open then - as its not solved and creates unexpected behaviour.

1 Like