Public Apps "Process Error. Process could not be started"

[argin.lerit]

Anyone else experiencing this error after deploying their Apps set to public access?

Process could not be started. Please check the configuration for this process in orchestrator or contact your admin.

I have the App deployed in the same Folder in the Tenant where the Process resides. Wanted to know if there are any others bumping into this issue?

Thanks!

[Anil_G (Anil Gorthi)]

@argin.lerit

Please check this

'Process could not be started' error (Public App Permissions and Roles)

To simplify management I created two roles. One that I assigned at the Tenant level: [image] And another for the folder level: [image] Then I made sure to assign the role for the Public App for the folder where my unattended automation was published: [image] What that looks like on the actual assignment screen: [image] You can validate that you’ve assigned these roles properly by checking the roles for your app under ‘Manage Access’ in Orchestrator: [image] pro-tip: when searching …

Hope this helps

Cheers

[Arvind_Kumar1 (Arvind Kumar)]

@argin.lerit ,

There is a glitch seems, Process never start from Public apps, I have faced this issue into past and reported it.

@evan.cohen @Venkata_Rajendran

Thanks
Arvind

[Ayush_Jain]

@Arvind_Kumar1 Just to confirm - are you providing the permissions as suggested by @evan.cohen ? For details you could refer to this documentation https://docs.uipath.com/apps/automation-cloud/latest/user-guide/use-public-apps - near the last section in this doc it specifies which permissions you need.

[Arvind_Kumar1 (Arvind Kumar)]

@Ayush_Jain ,

Yes we have given all the tenant and folder level permission.