Answered

Cloud run locator timeout limit

Dhrupa Patel

October 15, 2020 13:09

To avoid test failed due to timing, we tried to set verify elements web locator to retry 20 seconds with 1s interval. We also set locator timeout to 20 in the execution setting. However, we occasionally get error message, saying our setting has been overridden. "New Attempts Amount: 10. New Interval: 1 second(s)".

My question is: why this is overridden? is there a way for us to set universal timeout to 20 tries. What other work arounds are available for us to avoid test failed due to some web element occationally only properly loaded after more than 10 seconds?

1 comment

Joseph Hamdan October 15, 2020 13:51

Hi Dhrupa,

The default limits are 10 attempts and 20 seconds intervals, so using anything above the default limit will cause the default limits to override the limits you entered, hence you will see a message like the one you mentioned. These limits can be found in Administration -> Account Preferences -> Timeouts. More information is found on this page.

But since you are using only 1 second as interval, you can use up to 20 seconds and therefore your test will verify the element 10 attempts and each attempt will take 20 seconds up until the element is visible. Please let us know if this works.

Regards,

Subject7 Team

Please sign in to leave a comment.