We are getting this error (1042) Script run timed out (measured actual run time) from couple of monitoring stations (Los Angeles and Ashburn)
We have around 8 scripts which are showing this error intermittently from only these two monitoring stations.
The same script monitors are working fine from Melbourne station.
We have tested these scripts locally using Jmeter, and we don't see any issue
We like to know why this error is occurring from monitoring stations (Los Angeles and Ashburn)?
Release : SAAS
Component : APP SYNTHETIC MONITOR ENVIRONMENTAL
This is most probably caused by the target website using an IP whitelist and blocking addresses of new monitoring stations.
Notice that stations Ashburn, UB, and Los Angeles, LL, keep failing, while Ashburn, L5, and Los Angeles, LA, succeed.
So, you need to check if the new monitoring stations IPs have been whitelisted at your side.
login to https://asm.ca.com/ and check the following page for monitoring stations IPs: