Not sure if this applies 100% to your situation, but we applied a hotfix to our players that replaced the SolarWinds.SEUM.Player.WatiN.dll with a new version to address playback issues. Support indicated that it was a necessary patch for 220.127.116.110 build of the player. This hotfix wasn't visible on the portal for us, so I am not sure its generally available.
settings that affect various timeouts during playback are in <PLAYER_INSTALL_DIR>\Solarwinds.SEUM.Agent.Worker.exe.config in <playerConfiguration> section and they end with "WaitTimeMs" suffix.
- elementWaitTimeMs - Time for which playback waits for an element that he should click/write/do something with. Lowering this value can speed up playback of transactions that are failing but it can cause false alerts for transactions where page content is not loaded fast enough.
- fileDownloadWaitTimeMs - Time for which playback waits when initiating file download. When server does not start sending file during this time, playback fails.
Other WaitTime values should not directly affect playback speed and should not be changed except specific situations.
Thanks. I have been tweaking those for some time and it has helped. But in this particular case, I was hoping for a setting to tell WPM to stop retrying a particular step after X failures.
IE, limit the number of times it does this:
2013-04-29 10:30:39,656 [SolarWinds.SEUM.Agent.Worker.exe][Browser Thread] WARN SolarWinds.SEUM.Player.WatiN.WatiNPlayer - Browser was stuck with pending requests for more than 10000ms.
Since it seems to just do it over and over and over before finally just failing the transaction.
In these cases, it is tying up one of the SEUM users for a long time and causing the player load to go up quite a bit.
I actually had that one set to 5000ms for a bit instead of 10000ms, but it didn't seem to make a difference at all in this case, the amount of time that passed between the start and stop of the step was the same.
So there seems to be an overall setting somewhere on how long it will give a failing step before giving up.
If you see pending requests message over and over, it may mean that browser is waiting for the main request for the page, not just some background requests. This wait time can be changed by setting value to "mainPageRequestWaitTimeMs" attribute in configuration file. However lowering this value may cause false alerts for pages that take longer to load.