Element Timeout Settings

Solved1.92K views
2
0 Comments

Hi all,

I'm not very sure how the timeout settings work and I wasn't able to find much info from the documentations. Please refer to the screenshot below.

Does this mean that it would take 300s (10 retries of 30s each) for a command to get no response before the timeout is triggered?

Also, how does the 90s TimeoutElement value work with the command timeout?

Would the 90s overwrite the 300s value? Would the total effective timeout window be 390s? Any help is greatly appreciated!

Thanks in advance!

Ben Vandenberghe [SLC] [DevOps Enabler] Selected answer as best 7th April 2022

3 Answers

2
12.55K 1 Comment

Hi Jackson,

There is a nice explanation available on this in the administrator training track.

You can find the video on element settings here.

Ben Vandenberghe [SLC] [DevOps Enabler] Selected answer as best 7th April 2022
Bert Vandenberghe [SLC] [DevOps Enabler] commented

Following the explanation of this video, it means it would take 30 seconds before the first command gives a timeout. From that moment onwards, the 90 seconds element timeout will count down. So, in total it would take 120 seconds before the timeout is displayed on the element and a timeout alarm is being generated.
You are viewing 1 out of 3 answers, click here to view all answers.