This exception is faulting the job instead of triggering the Catch block

With a variable of datatype IEnumerable<String> and using the yourVar.Concat({"Add this value"}) expression, if yourVar is not initialized (ie New List(Of String) then it throws this exception:

image

However, this immediately faults the job. It is not caught as a system nor business exception by the Try Catch.

Which Studio & package versions are you on?

We are on version 23.4.4 of both.

Hi @postwick ,

Is it possible to share the screenshot of the workflow or the Catch part sequence ?

I’m not looking for help here, I’m reporting a bug. There’s nothing wrong with the automation nor the Try/Catch. It was all working fine until I added this one expression and forgot to initalize the IEnumerable.

@efelantti ,

The screenshots or the implementation would help for us to replicate the issue properly from our end as well and confirm the Bug.

It’s just an assign.

Assign yourVar = yourVar.Concat({“Add this value”})

If yourVar is not initalized (ie New List(Of String)) then it throws an exception.

@postwick

Can you please check may be in your catch you are usign that variable again?

tried replicating same in two versions that I have 22.10 and 23.12 with package of 23.4 and no issue as such

cheers

Can you indulge us and show the try catch? Specifically the catch?