Automation Co-Pilot for Business Users FAQ

Answers to frequently asked questions (FAQs) for embedded instances of Automation Co-Pilot.

When using an embedded interface of Automation Co-Pilot, content is passed from the Automation 360 platform to the iFrame that surfaces in your host application. If users need to trace an issue, key areas to examine are configurations of: host application, browser, and Automation Co-Pilot.

Disable third-party storage partitioning

Based on your Control Room version, Automation Co-Pilot users might need to disable third-party storage partitioning from browsers (such as Google Chrome or Microsoft Edge) to enable communication to the embedded iFrame.

Partitioning can cause users to experience the following issues:
  • The user enters credentials into the Log In window. However, the Automation Co-Pilot screen displays a spinning wheel and does not progress. This is because communication between Google Chrome and the iFrame are partitioned and do not transfer data.
  • A user logs in successfully and a window displays for Automation Co-Pilot. The Log In window does not close and the Automation Co-Pilot window displays a spinner.
As of Control Room version v.32, Automation Co-Pilot functionality is included in the Control Room domain. Based on your Control Room version:
  • If your Control Room version is v.31 or earlier, you should disable the partitioning flags.
    • If your Google Chrome is M129 or later (or your Microsoft Edge is M130 or later), enter the command-line switch to turn off storage partitioning: --disable-features=ThirdPartyStoragePartitioning. See command-line switch for details.
    • If your Google Chrome is earlier than M129 (or if your Microsoft Edge is earlier than M130), then you must set the internal flags to disable third-party storage partitioning:
      1. Navigate to the appropriate browser partitioning location:
      2. Select Disabled from the drop-down.
  • If your Control Room version is v.32 or later, then ensure that the iFrames for Automation Co-Pilot have been configured using the /copilot URL path and not the previous /aari/#/embedded URL.

Allow pop-ups from Automation Co-Pilot

If the end users is not seeing the Log In window, it could be that the browser is blocking pop-up windows. The end user should add Automation Co-Pilot as a pop-up exception.

To manage pop-ups in Google Chrome:
  1. From Chrome, navigate to a page where pop-ups are blocked.
  2. In the address bar, click Pop-up blocked.
  3. Click the link for the pop-up you want to see.
  4. To always see pop-ups for the site, select Always allow pop-ups and redirects from [site] > Done.