Getting error trying to start a process via app

[GlennRoberts]

I am getting the following error when trying to start the process from an app - unable to create orchestrator webhook with message: You are not authorized! and error: {“statusCode”:403}

within the app the user permissions have been granted.
Within the tenant and folder the user has automation user and the allow to be automation user permission.
The robot can be started manually by the user within the folder.

Any help would be much appreciated.
Thanks
Glenn

[Nithinkrishna]

Hey @GlennRoberts

Did you make the Authorization right and got the access token?

Thanks
#nK

[GlennRoberts]

I am unsure what you are asking here nk.

I am using a uipath app so there is no need for a token to allow authentication unless this has changed recently

[Nithinkrishna]

Hey @GlennRoberts

Sorry, I was thinking a web app.

Just check your tenant webhooks if you have already created many of them ?

Thanks
#nK

[GlennRoberts]

Hi NK.

How would i go about this.

Previously when creating UiPath Apps i simply connected to the process and i have never required to do any extra steps

[Nithinkrishna]

Hey @GlennRoberts

Yes you are right.

It’s still the same. But i feel you would have reached the limit may be for webhooks.

That’s what I suspect.

Thanks
#nK

[GlennRoberts]

Thanks will look into this

Do you know what the limit for webhooks is?

Thanks
Glenn

[GlennRoberts]

Hi NK looked at the limit which is 100 - unfortunately we are only at 37

[Nithinkrishna]

Hey @GlennRoberts

Looks weird screenshots please?

Thanks
#nK

[Arvind_Kumar1 (Arvind Kumar)]

Did u check webhooks configuration?

Have you selected correct event and permission? Please check this once else delete the webhook and re-add

Remove permission and re-add .

Thanks,
AK

[GlennRoberts]

We have resolved the problem,

We added an extra role for creating webhooks and assigned it to the affected user.

However the developer who was creating it was previously experiencing this problem but has since been resolved on its own. They were not assigned with the new role and had the same permissions on the folder as the person attempting to use the application.

Thanks
Glenn

[Nithinkrishna]

Cool @GlennRoberts