Hi @pablo 2030 ,

You can check two things here. 

1. Check whether the Runner user has Locker_Consumer privilege. If not, create one and assign it to the User.

or

2. If this User is the Locker Participant, check whether you have given the Credentials in the Credentials Request page under Manage → Credentials. 

Thanks for your reply @Padmakumar 

Can you explain me how to check my privileges (Locker_Consumer privilege) ??

This role will not be there at first. So, you can either create one or can add below mentioned features to any of the Custom role which you have already created. Later, just add this role to the User if it is not assigned yet.

1. View dashboards.
2. View my activity.
3. Manage my credentials and lockers.
4. Create standard attributes for a credential.
5. Create standard attributes for a credential.
6. View and manage my Bot runners, Bot creators and device pools.

 maybe the Locker_Consumer privilege doesn’t exists in Community Edition (only in professional).  is this true??

my unique user has the privileges:

and I can’t create additional users:

@pablo 2030 

  {"code":"access.is.denied","details":null,"message":"Access is denied"}

Cause

Checked and found the user was not having locker consumer role assigned to access the credentials.

Resolution/Workaround

The solution is to add the RunAsUser to the custom role that has locker consumer permission and then the bot needs to be deployed.
-OR-
Assign the User locker consumer role who wants to access the credential variables.

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/control-room/bots/credentials/cloud-create-locker.html

@pablo 2030 

Try to recreate the Credentials and test them again. 

Regards

Thanks for your replies:

@Raul Jaimes,

I remake the same robot, i’m still without access to my credential (user):

If I set “normal” text (keystrokes) the bot runs OK, but if I use credentials the bot fails . What’s the problem???

@rbkadiyam,

I needed to edit my locker and add my role as consumer, now the bot runs OK with my credentials¡¡¡¡