Global settings are the default settings used by each conductor.
Custom settings are available to define different settings for a particular conductor, for example to specify a specific logout mode.
| Setting | Description |
|---|---|
|
Logout mode |
The logout mode defines the agent behavior after a task is complete. Logout after every task: Logout after each task is completed. Recommended if multiple agents work on the same conductor. Logout when idle: Logout when the agent cannot find a new task. Restart when idle: Reboot the conductor if the agent cannot find a new task. After reboot, RPA Conductor searches for tasks for all active agents on the conductor. Shutdown when idle: RPA Conductor first signs out of the agent if there are no tasks pending for the agent and then shuts down the conductor if the agent cannot find a new task. Stay logged in: The agent remains in the window's session until a next task is found. This setting is recommended if you want to automate as many tasks as possible. |
|
Log level |
Defines the minimum log level written into the RPA Conductor log. The user can select from the following log levels:
|
|
Log Limit |
Maximum number of log files stored on the Client. |
|
Log Location |
Specifies the location of the log files on the Client, including the name of the file you want the log to be saved as. You can either specify a fixed or a relative path. Examples
Note: If the specified folder does not exist on the computer, it will
be created.
|
|
Update Interval |
Interval at which RPA Conductor checks for updated settings. After changing a setting, it takes at most as long as specified in the setting for it to become active. |
|
Check for task when idle |
Interval at which RPA Conductor checks for new tasks when idle. For example, when no task was returned immediately after task execution. |
|
Status check when paused |
Interval at which RPA Conductor checks if its status has changed when the conductor is paused. |
|
Conductor Working directory |
The working directory is a folder where RPA Conductor stores downloaded activities and process files needed for task execution. |
|
Wait time after login |
This setting determines the time RPA Conductor waits between logging on and starting the process. If it takes too long until a Windows session is ready to work, you can increase the default time. The default value in RPA Conductor is 10 seconds. |
| Heartbeat Interval | Specifies the interval at which RPA Conductor sends its connection status to the RPA Platform. |
|
Use proxy |
Determines if the Conductor service should use a proxy to communicate with web services. Provide the proxy server information in the following format: |