Studio Pro and Bot Runner can register logs about each workflow you run. Here are two options for you to collect and save this data with Orchestrator SaaS.

Collecting execution logs

Orchestrator SaaS can collect execution logs automatically. This data shows every execution of the bot. Follow these steps to enable this option:

1. Navigate to the "Orchestrator SaaS" page of the User Portal.
2. Open the "Workflows" tab.
3. Select a workflow.
4. In the list of parameters, enable the "Collect execution logs automatically" option.
   
   
   
   
5. A confirmation window displays. Click "Confirm".
   

Checking results

If the option is enabled, you can see execution logs after running the bot. To do that:

1. Navigate to the "Workflows" tab.
2. Go to the list of workflows and click on the desired one.
3. Go to the "Runs history" tab.
4. Among the list of launches, choose one and press the "sheet" symbol to see its logs.
5. Click on the "Automatic logs" tab.

To download logs as CSV files, click "Save to file".

Collecting console logs

As of version 8.5 of Bot Runner, users can collect data obtained from the Console log activity in the workflow. 

This Studio Pro activity allows you to see information such as time, warnings, success messages, errors, etc. From these details, you can check, for instance, if a business parameter fails and then a business owner with an Analyst role in Orchestrator SaaS can access the platform and see what happened.

Checking results

If the logging option is enabled, you can see bot logs after executing them. To do that:

1. Navigate to the "Workflows" tab.
2. Go to the list of workflows and click on the desired one.
3. Go to the "Runs history" tab.
4. Among the list of launches, choose one and press the "sheet" symbol to see its logs.
5. There you see the "Console logs" tab.
   

Click the "More information" icon to see more details in a pop-up: