ShoulmarkJob as faullted in Reframwwork

[NaveenKNave]

Hi All,

Could you please explain in detail, how below condition will work in reframework. If any system exception, will it mark job as faulted?

and “Terminate Workflow” activity is responsible for marking faulted job in orchestrator?

[Somanath1 (Somanath Aland)]

Hii @NaveenKNave ,

In REFramework, a system exception does not automatically mark the job as Faulted in Orchestrator. Instead, it retries the transaction (if enabled) or moves to the next one. The job is only marked as Faulted if the process crashes due to an unhandled exception or explicitly uses the “Terminate Workflow” activity. This activity is responsible for faulting the job in Orchestrator. By default, REFramework logs exceptions and continues execution. To force a Faulted job, add “Terminate Workflow” in the System Exception block of Set Transaction Status.xaml after logging the error.

[NaveenKNave]

Hi @Somanath1 , thanks for the explanation. could you please provide usage of “ShoulMarkJobAsFaulted” row in config file (constant-sheet).

By default it is False, if change to “True” , if incase of system exception in Init state will job mark as faulted ?

[Anil_G (Anil Gorthi)]

@NaveenKNave

So in the intialization stage if there is an error that is at start of process or if max consecutive exceptions is reached which again is controllable from config can set to 0 if you dont want to then the terminate workflow activity in end prpcess will terminate the process and mark the job in orchestrator as faulted

Cheers

[sharazkm32 (Sharaz K M)]

@NaveenKNave

As mentioned in the config description
“Must be TRUE or FALSE. If the value is TRUE and an error occurs in Initialization state or the MaxConsecutiveSystemExceptions is reached, the job is marked as Faulted.”

This value is used in the END PROCESS State in the final block of Close All Applications. As highlighted - If a process failed in the initialization stage or end after continues error in transactions, it will execute the END PROCESS State. In the end if the above value is set as true - BOT will terminate the workflow which will create a status as Faulted in the final status of the job run in orchestrator.

I would suggest you keep it as True only

[mkankatala (Mahesh Kankatala)]

Hi @NaveenKNave

The ShouldMarkJobAsFaulted value in the configuration file determines how the job handles system exceptions. If set to True, the job will be marked as faulted when a system exception occurs during the initialization phase or when the maximum number of consecutive system exceptions is reached. If set to False, the job will not be marked as faulted and will instead be marked as successful. However, in this case, you will only be able to identify if a system exception occurred during initialization or if the maximum consecutive system exception limit was reached by reviewing the logs.

It was handled in End Process state, check the below image for better understanding,

Terminate workflow will Terminate the workflow so it sets job as faulted.

Hope it helps!!