Bot deploy started failing after modification and check-in to the AA360 control Room

Hi!

TL;DR: If a task is new, everything works. If the task is Modified, the bot will not deploy on the runner VM.

A consultant working for us reported yesterday to me (Control Room administrator) that one of their bots was not working after a very small modification in the code (they just recaptured one object using the recorder package). Instantly I saw that the reason was a Deploy Failure and looked for the logs.

Apparently, the reason for the failure is that the runner user “don’t have access to the folder”, but it is the same bot as before. To workaround this, they created a new task, copied all the actions and changed the references to that new task in the same folder, and everything started to work again.

But, today they made another similar adjustment in another subtask of the same bot and again, the deploy is failing after they make the check-in to the control room.

Have anyone been experiencing the same issue recently? I know there is an article with around 26 probable causes for this error and I have already read it, that’s why I got to the Node-manager logs and can tell you that the cause is #24 and the error is related to folder permissions. None of the permissions where modified in the control room and they are using the same bot creator user.

Thank you for reading!