Hi Yining.  I thought this might be you.  Great to hear from you again -- I guess your life, like mine, is Pega forever!  ;)

Your example is correct, but depending upon the actual behavior, and the reason for detecting "failure", it might be good enough.  It depends upon what the expected or observed behavior of the pages might be.  In a simple case, you expect each page to take no more than 2 seconds.  If you configure all the Connect-Waits for 2 seconds, and the actual load times are 2,2,2,2,2, then step 10 will wait 2 seconds, and steps 11-14 won't wait at all -- the loading will have been completed by the time you get to them.

If Step 13 takes 5 seconds when normal expectation is 2 seconds, then step 10-12 will succeed, and 13 will fail.

Or, if you observe that when a page fails to load, it NEVER loads, then again, having the 4 connect-waits will catch each of the failures.

For your scenario, I agree we would only see step 10 fail, unless, of course, step 14 is so slow it fails anyway.  If you fall into the middle ground, where both 10 and 14 each take 10 seconds (so they each have exceeded their expected load time), what is the purpose of detecting "failure"? For, although in this case step 14 failed to load within the expected 10 seconds, it did actually load.  If it did not, you would see that step 14 failed as well.