Get name sub process that error

Help Activities
, ,
1

Hello.

I want to get name sub process (invoke workflow file) that error.

Please guide me for solve it.

Thank you.

2

hello @Stef_99
Can you explain your requirement in more detail?
regards

3

@dheerandra.vishwakarma Now I have try catch for control error and get activity name that error ( exception.source)

But now I want to process name that error.

My flow have main workflow and use in invoke code.

Please guide me for solve it.

Thank you

4

Can you please explain clearer to help you out.

6

@Stef_99,

Retrieving the workflow name which is faulted is not feasible but you can add two logs, one at start of each workflow file and another at end of the workflow file.

Whenever any error occurs in any workflow you will be able to identify it by looking to log like what was the last workflow started but not finished. That’s your culprit.

Thanks,
Ashok :slight_smile:

7

@ashokkarale I have invoke code have argument “out_srt_subProcessName” in catch block
image
image

but value in main show null.

Please guide me about it.

8

@Stef_99,

Check if you have out_srt_subProcessName as variable as well because arguments are perfectly configured.

9

@ashokkarale value out_srt_subProcessName in​ login flow​ have​ data.

Is this relate​ in​ case go​ to​ block catch​ or not?

10

yes. This will only return workflow name if catch block executed.

May be you can assign this at the start of workflow.

1 Like
11

@ashokkarale assign in​ try​ block?

12

@Stef_99,
Before try also would be fine but if you don’t want anything out of try catch, just put it in try block

1 Like
13

I solve this by using a log message at the beginning and end of each workflow with its name
also, run it in debug mode to see why the output is null maybe you used it twice or something like this

1 Like
14

To get the name of the subprocess (the file with the workflow call) in which the error occurred, you should do the following: Open the error log or process execution logs. Look carefully at the error messages and look for any mention of the subprocesses or files in which the error occurred. Make a note of the file or subprocess name that is listed in the error message. You can then find and fix the problem in the corresponding file or subprocess.

15

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.