I have an activity to click image if it cannot find the image it throws an exception and source field in the exception pop up tells me exactly which image(My Display name) is throwing the exception.But when I catch that exception, exception.source property gives me system.activities as an Output. …

yes, check this here. Logging.zip (7.6 KB) [image] Component/Sequence/Workflow Name Studio Moved it to ideas. What do you mean by component? For exception logging you can use exception.Source property. Run the main.xaml in the attached example. . Logging.zip (7.6 KB) Oth…

Try exception.Tostring or exception.Message.

Both Try exception.Tostring or exception.Message says Image not found.It doesn’t say explicitly which Image

True. It seems to be a bug.I think you can capture the Displayname in a variable or hardcode in that specific exception. @badita can you help

So what you are saying is, if we want to have the name of the activity, we need to have all error handling in another workflow, like: workflow: RUNME try{ invoke main } catch all exceptions{ Print activity name} Is there really not smarter solution? If not, could there be an option when start…

Hi badita, I appreciate your sharing knowledge for logging exception.source. Couldn’t we log exception source when we use only 1 workflow which don’t have [Invoke workflow] ? Regards, Soshi

As of now…no. We are limited by the WF technology.

Hi @badita , This solution provides us the activity name in which the exception occured. But if I have multiple files how can I know in which file this exception occured? Is there any solution for us to know both the below things. I want to know activity name in which the exception occured Also …

It might be helpful to store like a destination variable before each Invoke, so you know where it is in the process. Then you can use that to know which part of the process failed and attach that with the Source and Message. However, depending on your framework, if your Try/Catch is outside of your …

Try Catch Printing Exception Source

Help

badita (Mihai Badita) March 9, 2017, 9:00pm 5

yes, check this here. Logging.zip (7.6 KB)

Only that it works only if the error occurs in an invoked workflow.

Therefore

do your actions in wf1
in main add try {invoke wf1;} catch(exception ex) {log ex.source};
run main

and it will work.

How to get Exception source "Activity Description name"

How to get a display name of activity that gave error using try catch

Try/Catch - exact source of exception is not shown

Killing a process if a job failed

Catch every error inside a workflow

Exception Location

Try Catch: What fields to log within Exception Object

Exception Handling example

How to get actual message of activity from throw activity?

Topic		Replies	Views
Try/Catch - exact source of exception is not shown Help studio	9	3661	June 18, 2018
Exception Location Help studio , debug	10	7637	January 25, 2018
How to get Exception source "Activity Description name" Help uiautomation , studio	21	31253	November 21, 2022
How to get a display name of activity that gave error using try catch Help studio	8	13329	March 28, 2018
How to know exception was generated from which activity? StudioX studiox , question	2	474	December 26, 2023

Try Catch Printing Exception Source

Related topics