Exception is Logged from Invoked Workflow automatically


Is this intended?
Exceptions from Invoked Workflows are being automatically logged as “Errors”, regardless if they are surrounded by a Try/Catch

Steps to reproduce:

Surround an Invoke Workflow File with a Try/Catch, then Throw an exception from the invoked workflow file.


Invoked File:

Current Behavior:

Output Pane:

Expected Behavior:

From my understanding, no exception should be logged automatically if surrounded by a Try/Catch. This can cause duplicated log messages, if you are using a framework that provides logging inside the Catch.

Correct me if I’m wrong.

Studio/Robot/Orchestrator Version: 2018.4.3

OS Version(s):
Windows Server 2012r2
Windows 7 Pro
.NET Framework Version 4.6.2


1 Like

Hey @ClaytonM

I added this issue to the tracker and it’s been resolved as by design with the following comment:

We should log all exceptions when they occur. This is invaluable information for troubleshooting, debug and analytics.

Just to keep you updated that it will stay as it is now :slight_smile: