How to check which orchestrator runs the job

Help Studio
1

Is it possible which orchestrator started the job of current process inside this process (or to which orchestrator machine is connected to). I would like to make some “ifs” in robot code to perform different activity for test and production orchestrator. specifically, I’d like to use a different file “Config” file for test and production.

2

Hello @MaciejSartys!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff

3

Hello!

One way could be making a HTTP request to one of the /odata/Settings endpoints of the Orchestrator API.
In your case, the endpoint /odata/Settings/UiPath.Server.Configuration.OData.GetConnectionString() might be helpful to differentiate between Orchestrator instances.

Note that you have to use the Orchestrator HTTP Request activity for those requests to make sure the data is coming from the Orchestrator instance to which the robot is currently connected.