• Gomez Recorder





First thing you could do is to view the screen for the failed step. Where the error occurs, the DOM tree is not completely built up resulting in an incomplete screen. For example, if the page is made up of a multitude of frames, you may notice that the contents of a certain frame are missing leaving the part of page blank. Secondly, you would notice that there are missing objects by viewing the http headers for that step. Thirdly, when you search for certain contents in the unaltered source code, no results return.

Once this occurs, you can add a Wait for Validation after the Page Complete Wait to the step where it fails. Below are the steps.

1) Add a Wait by clicking on the plus icon beside the Page Complete wait
2) Choose 'Validate' for wait criteria, feed a page element to validate by filling out the following contents:
- Match Text: The text to find within that element.
- Target Window: The target window where that element locates
- Locator: DOM or CSS locator

You can input Match Text the same as Validation text. Here's a good tip to find what to enter to validate. You can copy the Target Window from the target window of the first click action of the next step as well as Locator. Put the text contents in the locator into the Match Text field. Because the actions of the next step depend on the page source of the current step, you can feed the element from the next step to validate if the current page is fully loaded.

Root Cause



Error rendering macro 'kbsurvey' : null

  • No labels