topic Re: 1301 - Hard Timeout in Synthetic Monitoring

1301 - Hard Timeout

sanjiv1987 — Tue, 13 Apr 2021 13:41:04 GMT

Hello,

Currently Iam facing the below error when Dynatrace is doing a playback.(Browser Monitor)

The errors are random and there is no specific pattern. Can someone please provide their inputs to fix this problem.

Not sure if a specific page where it loads is taking some time.

Iam using "Wait for background Network activity to get completed" option.

How to fix these random errors.(When some pages load slowly)

Re: 1301 - Hard Timeout

HannahM — Mon, 02 Dec 2019 08:39:31 GMT

Hi Sanjeev,

perhaps try using a different wait. If your page has videos or lots of background activity it is possible that the background activity will never stop. Possibly Wait for a specific element for the next event.

Best wishes, Hannah

Re: 1301 - Hard Timeout

lamberk14 — Mon, 30 Aug 2021 20:45:59 GMT

I'm getting the same error... but it seems to happen at the same time periodically. Only have 3 days of sample. Just found it today. Trying to find out more.

Re: 1301 - Hard Timeout

olga_wall — Fri, 25 Mar 2022 14:55:07 GMT

Hi,

to understand the meaning of the "1301 - Hard timeout" error in the context of browser monitor better: Does this mean that the wait times of all recorded events have summed up to the hard excution time limit of 5 minutes?
Thanks,

Olga

Re: 1301 - Hard Timeout

HannahM — Fri, 25 Mar 2022 15:05:22 GMT

Hi Olga,

yes, exactly that. The Hard timeout for a Browser Monitor is 5 minutes. Can you change some of your waits? Usually that helps. I find 'Wait for Next' event particularly helpful in these cases as the monitor can move on a little quicker.

Re: 1301 - Hard Timeout

olga_wall — Fri, 25 Mar 2022 15:06:37 GMT

Thanks for the tip, Hannah!

Re: 1301 - Hard Timeout

HannahM — Thu, 05 Jan 2023 15:33:13 GMT

If after you have tried other options, blocking slow requests that you are not interested in, updating the wait strategies etc, then it might be worth considering increasing the script timeout. I would definitely only do this as a last resort. You can find the documentation on this here.
bmMonitorTimeout - browser monitor execution timeout (ms)
maximum: 3600000 minimum: 60000

bmStepTimeout - browser monitor single step execution timeout (ms)

maximum: 180000 minimum: 10000