Skip to main content

I have the following problem: I developed a TASK API, and I can debug it without issues in the private workspace. However, when I move it to the public space, it shows me the following error when I try to run it. I'm leaving the image below. Could someone help me? Thanks!

 

 

The message says it all. “Only users with ‘Run’ permission for the folder can be selected as the Run-as user.”

This means your admin (or yourself if you’re the admin) needs to ensure that user has a role that allows for Run permissions in that public folder.

 


Thank you for the quick response. I apologize because the screenshot I sent was cut off. My user has permissions for everything, meaning I can run task bots normally. The problem is with the API tasks. I want to use the default user 'apitaskrunner' and the error appears. The same thing happens if I select my own user. In any case, I understand that it should already work with 'apitaskrunner'. I'm not sure if there's anything I need to do before running it in the cloud. The steps I took were the following:
1- I created an API task in my Private workspace, I was able to debug it perfectly and it works okay.
2- I moved it to Public in the Control Room.
3- I try to run it with the user 'apitaskrunner' and the error appears.

 

 


Hi ​@leandro.castello ,

 

Are you using any credentials from Credential vault within your task? If so, to ensure successful retrieval of credentials from a credential vault within your API Task, the run-as user selected in the API Task allocations table must have the View and edit ALL credentials attributes value permission plus a valid authorization key should be mandatory.

 

 

Note: Running API Tasks in Control Room requires Enterprise Platform license. For more information about supported version for this feature, see Enterprise Platform.


Thank you for the response. 

The Task API does not use credentials from the credential vault; on the other hand, the default user "apitaskrunner" cannot have its permissions edited as they are all assigned by default. 

We are still experiencing the same problem and we have an Enterprise License.


Updating information, I was able to find the solution, I needed to generate a key for the bot agent, I followed these steps:

 

 


Reply