Bug fixes​

• Fixed an issue where a timeout set on the Invoke Workflow File activity could intermittently let the invoked workflow report success instead of raising a timeout error. If the invoked workflow finished being cancelled just before the timeout error was raised, the invocation returned normally with empty output, so automations such as REFramework marked the current queue transaction as Successful instead of Failed.
• Fixed an issue where a timeout set on the Invoke Workflow File activity was silently dropped if it elapsed while the invoked workflow was still loading, leaving the invoked workflow running with no timeout at all.
• Fixed an issue where setting the UIPATH_FILE_LOG_LEVEL environment variable to Verbose did not add activity logs to the local execution log, because activity logging remained controlled by the log level configured in Orchestrator. As part of this fix, Trace now means the same thing on both targets, so a local execution log set to Trace no longer receives the activity logs produced for Verbose.

New features​

• Robot processes can now take their proxy configuration from the machine-level proxy.json file instead of the proxy configuration of the account running them, enabled through the new UIPATH_APPLY_SERVICE_PROXY machine environment variable. This lets unattended robots whose service account has no proxy configuration of its own use a machine-wide proxy, without configuring the proxy separately for each account that runs automations. For more information, see Using the machine-level proxy for all Robot processes.

Bug fixes​

• Fixed an issue where a long-running automation that could not create a Windows session while resuming was permanently faulted, losing the persisted job state. The job now returns to Suspended with its persisted state intact and the underlying error reported to Orchestrator, so it can be resumed once the problem is fixed.