The strange part is. Recording of failed queue transactions works when queue and process is stored in the same folder we normally use.
But with this queue I wanted to get some more order. So I got the process in our normal folder (package feed) and the queue in a tenant package feed folder.
This is what I found in the documentation. I specifically set that. As I’m folder admin I shouldn’t need to. But this doesn’t work also. Or I’m totally setting it wrong.
Permissions
This feature is controlled by the folder-level Execution Media permission, with the following options:
View - Allows the account to see job execution recordings.
Create - Allows the account/role that executes the job to also create the recording of the job execution.
Delete - Allows the account to delete video recordings from Orchestrator.
The default folder-level roles that include the Create permission on Execution Media are Folder Administrator, Automation User, and Robot.
After lots of different searches in google I found a solution with the AI of Dr. Google
Seems like I need to link the queue in the folder where the process is. And then I am able to see the recordings in the linked queue in that folder but not in the folder where the queue is.
I’m gonna mark it as solved. When we have our 2e robot I gonna place all stuff of a process together. Would make it more logical.