Errors "User Does Not Have Connections. View Permissions On The Connection Folder" or "Connection [*] Is Invalid Or You Do Not Have Access To It" While Running Automations With Integration Service Connections From UiPath Assistant Or In Unattended Mode

News Knowledge Base
, , , , , , , , , , , , , ,
1

Errors "User does not have Connections.View permissions on the connection folder" or "Connection [*] is invalid or you do not have access to it" while running automations with Integration Service connections in Attended/Unattended mode.

Issue Description:

A workflow containing Integration Service connections works as expected in the Studio machine where it is created. However, when the code/job is executed on a different machine, either from UiPath Assistant (Attended mode) or triggered from Automation Cloud Orchestrator (Unattended mode), the following errors are observed:

  • User does not have Connections.View permissions on the connection folder
  • Connection [*] is invalid or you do not have access to it

This error is observed even though the connections are shared via Connection Sharing.

Resolution:

This issue is generally observed for Studio versions below v2022.4.3. The first step is to ensure that the version of Studio/ Robot is v2023.4.3 and above. If the version of Studio is lower than v2023.4.3, follow the documentation to Update Studio.

Validating the connection status and connection sharing in Integration Service is also essential. The steps for the same are detailed below:

  1. Login to Automation Cloud and navigate to the connection in Integration Service. Click on Check Connection -> If is successful and the Status is Connected, move to Step 2Image_2023-09-24_10-50-55.png
    • If not, then the connection needs reauthentication/ fixing. Click on the Fix connection -> Connect. The below screen prints use the Microsoft Outlook 365 connector Image_2023-09-24_10-48-13.pngImage_2023-09-24_10-47-31.png
    • If the connection is not available or cannot be found, click on Add connection -> Select the connector -> Create the connection. The below screenprints use the Microsoft Outlook 365 connector Image_2023-09-24_10-50-01.pngImage_2023-09-24_10-49-36.png
  1. Go to Orchestrator -> Modern folder where the connection was tested and configured -> Users -> Unassign the Robot from the listImage_2023-09-24_10-52-54.png
  2. Add back the Robot to the Modern Folder where the Microsoft Outlook 365 connection was tested and configured and provide the role of 'Automation User' Image_2023-09-24_10-54-24.png
  3. Navigate to the Modern Folder where the Microsoft Outlook 365 connection was tested and configured -> Automations -> Find the previous failed process (make sure it is updated to the latest published version) -> Edit -> Package Requirements -> check if the Connection is set as default and if there are connection-specific issues (usually should display Connection is broken if you have issues) -> Fix the Connection issue -> Update Image_2023-09-24_10-57-31.pngImage_2023-09-24_10-57-15.png
  4. Try to run the new job again with the previously impacted Robot.



Another set of steps that can be performed in case the above steps do not resolve the issue:

  1. Create a custom Folder role with permissions for Connections and Triggers
  2. In Automation Cloud Orchestrator: Remove the user from the folder where the connection is present
  3. Sign out and Sign in to Automation Cloud Orchestrator
  4. Add the user back to the folder with the necessary roles. Kindly ensure the custom Connection role created in Step 1 is assigned to the user
  5. Sign out and Sign in to Automation Cloud Orchestrator
  6. The user should also sign out and sign in to Automation Cloud Orchestrator and UiPath Assistant on their machines.
Other identified causes for this issue are listed below:
  • Check the Project compatibility documentation and ensure that the activity package used is compatible with the project type.