Serverless Bots not working with Integration Service Activities

when I build a process with studio web or studio desktop, on cross platform, and utilize any connections in integration service, I get the same exception when I run on a serverless runtime in orchestrator:

One or more errors occurred. (Connection [b86b3e5c-109c-ed11-bf7a-0003ffe7e379] is invalid or you do not have access to it)

As it currently stands, because of this bug, I cannot use any integration service connections in a serverless automation, rendering serverless automations much less powerful.

1 Like

Hey @Mason_Turvey_Silver, Are you able to run the same automations with another runtime that isn’t serverless? Also, are your serverless bots set up in a folder within orchestrator where the IS connections have been created? It might make sense to hop on a call to troubleshoot.

Hey @Scott_Schoenberger,

I created the connections in the IS tab on automation cloud - not in a folder. I’m not aware of any way to create a connection specifically within a folder.

Basically my setup is this: Top level folder with package feed → lower level folder, both serverless machine template and service account are assigned to this lo\er level folder, under robot role (ensured this role has connections permissions). I create the connectors over in integration service and set up the connections (in this case google workspace). I then develop the code in either studio web or studio, and use the connection I set up in IS. Then deploy code to the folder ajd run on that machine template and svc acct.

I don’t have an unattended up and running to really test them unfortunately.

@Scott_Schoenberger I’d be happy to set up a time to hop in and troubleshoot. If you have a vm lying around, I have an unattended license that we can put it on ot test that avenue.

@Mason_Turvey_Silver, Product Support/@Michelle_Henriques is looking into this right now and will post her findings.

Hi @Mason_Turvey_Silver I was able to execute a job with an integration service on a serverless robot. The steps followed are as follows:

In Integration Service:
Created a connection with Salesforce.

In UiPath Studio:
Created a cross-platform project in UiPath Studio with the Salesforce Integration Service connection and published it to Automation Cloud Orchestrator.

In Automation Cloud Orchestrator:

  1. Logged into Automation Cloud with the account that created the above connections
  2. Created a process for the published project.
  3. Enabled Unattended Automation for the user (who created the Integration Service connection) in Orchestrator. Steps here.
  4. Added Serverless Robots to the tenant. Steps here
  5. Added the user and the serverless robot machine template to the folder where the process exists. Steps [here](https://Giving access to folder resources)
  6. Executed the job on the serverless robot. Steps here.

Point to remember: Currently, a connection created by a user in Integration Service cannot be used/shared with anyone else. Hence, the Unattended Robot has to be created under the same user who created the connection in Integration Services.

I will create a video demonstrating the above steps from start to end and will share the same with you soon.
Thank you!

Ahhh, so there is no way to create a serverless robot account and run the automations under said account. This makes sense, but also sort of defeats the utility of serverless automations.

Can’t wait for connection sharing then!

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.