I am not able to duplicate the issue, but your question is lacking in detail. Can you please answer the following to help us help you?

• Is the service you’re trying to trigger on a standard service, or one you created?
• Do you get this behavior on any service you try to trigger on, or just the one?
  • If it happens on any service, have you tried uninstalling/reinstalling Bot Agent on the machine?
• Have you tried pointing the bot runner at a different machine, different OS, etc. to see if the behavior is the same?

Hello ​@JLogan3o13, thank you for your response. I’ll try to provide more context to the issue.

1. The problem we are facing occurs on refresh options… step which should populate the list of services drop down menu. As such, this happers before I am able to choose specific Service (or Process for process trigger). To put it into context, this would be step 7 in “Add a service trigger” procedre below. https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/aae-client/bot-creator/working-with-automation-tasks/add-service-trigger.html
2. This happens for every user in our control room instance, both in already existing and new bots. It also occurs on every machine we have tried it so far. We also have reinstaled bot agent several times.
3. The important detail would probably be that we are running on premise CR instance with build 23234. Perhaps the issue would be lacking permissions of some kind.

Best Regards