Timout activitie dosn't work

Help Activities
, ,
1

Hello everyone.

I am experiencing an issue with the “Timeout Scope” in my automation workflow. I added the Timeout Scope around the section that attempts to connect to the database because, at times, this process gets stuck, and I haven’t yet determined the cause.
However, I noticed that the Timeout Scope did not function as expected yesterday while running on the Orchestrator. The automation remained stuck on the “Database connected” log for 16 hours
How i can find what happens?

This is my flow:

image
image420×681 21.7 KB

And this is the orchstrator log (with the 16 hours on “Data base conected.” log):
image

2

Hello

I have a suggestion to keep your process moving (but nothing for troubleshooting the root cause).

Take a look at this Parallel activity to throw an exception after 5 minutes.

857×799 60.8 KB

Steps

  • Insert a parallel and two sequence activities.
  • Create a boolean called Success with the scope of the Parallel activity. Default value: ‘False’
  • Insert your current activities into Left most sequence (minus the Timeout activity).
  • Insert a delay for 5mins and an If statement into the Right most sequence.

Explanation attempt :sweat_smile:

  • Yellow box indicates that these activities will run in parrallel for 5mins.
  • Blue underline shows a relationship between the boolean ‘Success’
  • Green shows happy path steps if the database activities are Successful in 5mins.
  • Red shows unhappy path to exception if the database activities are NOT successful completed in 5mins.

A con with this design is that the 5min delay will always be executed even when the database activities successfully execute.

Hopefully this helps

Cheers

Steve

3

Hi!

Is there a reason you’re using the Timeout Scope and not the Timeout property for the activities in your flow?

Could you check if there are any values in them that might add to your total timeout?

4

Hi Steven! Thank you for your detailed example. I will try using this approach instead of the timeout activity.

If it works, I’ll be sure to share the results here!

5

Yes, even when I use the Timeout property, the job still gets stuck on this log for some reason. I’m not exactly sure why this is happening, but I suspect it may be related to the connection between the Orchestrator and the VM I’m using.
I don’t know exactly how to find out why this “stuck” problem is happening.