Receiving 'Navigation timed out but sync point met.' message received from Foglight Transaction Player (FTP) agent.
When an http page is requested from a server part of the response from the http server is a count of the number of elements that are included in the page. Since web browsers do not have a function that indicates a page is complete FTR uses this number to count the number of elements that have been sent from the http server to the browser, when the number of elements sent equals the number that the https server sent FTR marks the page download as complete. When fewer elements are sent then the count from the server FTR waits for the additional elements until the step times out. Then if the element that FTR is trying to use (click, verify, etc) exists on the page, FTR will continue the script with the message page timed out but sync point met.
If the element that FTR is trying to use is not sent the step will fail.
If you do not want to receive alarms for this message there are 2 options to address this issue.
1. You can adjust the timeout on the offending instruction by hand to a larger value. Within the Foglight Transaction Recorder (FTR) you can right-click on the instruction, select Properties, and then increase the value in the Time Out field.
2. In the V5.X FTR you can use the Error Overrides setting in the FTR to add the error number you are getting, and set the severity to Info level instead of the warning level. After adding the error number and setting it to an Info level the error will not generate alarms in Foglight. These error overrides are per script so if you have more than one script with that message, you will need to change them all.
To add an Error Override right-click on the first icon in the script, select Properties, and edit the Error Overrides setting.