Skip to main content

Attended Robot Failed to Start

Article # 308096 - Page views: 804



This Knowledgebase article details an issue related to running an Attended robot (Trigger robot)

More Information


When attempting to call a robot using a trigger (on the Desktop Automation machine (DAS)), the robot fails to start.

The error notification is similar to:


and in the DAS logs show:

DEBUG DAS - Could not start trigger.  null . Management Console status:  nok



This is a known issue in v10.5.0.0 and earlier and is related to the " Access-Control-Allow Origin" setting for the project containing the robot.


  • On the Management Console navigate to Admin > Projects
  • Open the configuration of the project containing the Trigger robot
  • Go to the Services tab
  • Make sure " Access-Control-Allow Origin" is empty (delete content and save the settings otherwise)
  • Restart DAS and re-try to call the robot.

Applies to:  

Product Version Category
RPA and earlier Attended Automation


Author:  Delia Milchis