For Browser Monitors, there is an option to increase the event and monitor timeout for both playback and execution on private locations. This is described in the information box here.
Before increasing the timeout I would take a look at why the monitor is hitting the hard timeout. Are the pages loading as quickly as you expect? Have you added in waits that are not really needed? Often we can decrease the time a script takes to run by changing the waits. You can see the descriptions of the different wait strategies here. Wait for specific element to appear or Wait for next event are usually good options to try in this scenario.
That said, if you just have a really slow site and the monitor needs to navigate across many pages you may find you need to increase the hard timeout. We added an option to increase the hard timeout for Browser Monitors. It is only available in the API and you can find the documentation here.
bmMonitorTimeout - browser monitor execution timeout (ms)
maximum: 900000
minimum: 60000
bmStepTimeout - browser monitor single step execution timeout (ms)
maximum: 180000
minimum: 10000
Synthetic SME and community advocate.
