The following is an extract from the LoadRunner User Guide (Recommended reading for all Performance testing engineer)

**How to Synchronize Ajax TruClient Scripts Steps:**

**Before enhancing an Ajax TruClient script, replay the script to synchronize the steps. During the first script replay, TruClient will try to automatically identify the End Event for each step.**

An End Event can be one of the following:

**Action Completed.** Step ends when its action is completed. An example of an action is a
button click.

**DOM load**. Step ends when the process of loading a document completes.

**DOM content loaded**. Step ends when the HTML parsing of the document completes.
HP Virtual User Generator User Guide

**Step network completed.** Step ends when all HTTP requests have completed including
requests initiated by XMLHttpRequest.

**Step synchronous network completed.** Step ends when all HTTP requests have
completed excluding requests initiated by XMLHttpRequest.

**Dialog opened.** Step ends when a dialog is opened.

**Automatic: Not Set Yet**. The automatic end event has not yet been determined.
If during the first replay, a step initiates the Object Identification Assistant to resolve object
identification, the previous step's End Event will most likely be misidentified and TruClient will
automatically reset it to Automatic: Not Set Yet

**Confirming the End Event**

During the second script replay, TruClient confirms the Automatic End Event and will assigned
any step's End Event that had been reset to Automatic: Not Set Yet.

If TruClient is unable to assign an automatic End Event during replay, usually due to a network
timeout, a warning message will inform you that the End Event has been reset to
Automatic: Not Set Yet.

Replay the script to automatically assign the End Event or assign the End Event manually.

**Note:** You may need to replay the script several times until all steps have been accurately
synchronized

The following is an extract from the LoadRunner User Guide (Recommended reading for all Performance testing engineer)

**How to Synchronize Ajax TruClient Scripts Steps:**

**Before enhancing an Ajax TruClient script, replay the script to synchronize the steps. During the first script replay, TruClient will try to automatically identify the End Event for each step.**

An End Event can be one of the following:

**Action Completed.** Step ends when its action is completed. An example of an action is a
button click.

**DOM load**. Step ends when the process of loading a document completes.

**DOM content loaded**. Step ends when the HTML parsing of the document completes.
HP Virtual User Generator User Guide

**Step network completed.** Step ends when all HTTP requests have completed including
requests initiated by XMLHttpRequest.

**Step synchronous network completed.** Step ends when all HTTP requests have
completed excluding requests initiated by XMLHttpRequest.

**Dialog opened.** Step ends when a dialog is opened.

**Automatic: Not Set Yet**. The automatic end event has not yet been determined.
If during the first replay, a step initiates the Object Identification Assistant to resolve object
identification, the previous step's End Event will most likely be misidentified and TruClient will
automatically reset it to Automatic: Not Set Yet

**Confirming the End Event**

During the second script replay, TruClient confirms the Automatic End Event and will assigned
any step's End Event that had been reset to Automatic: Not Set Yet.

If TruClient is unable to assign an automatic End Event during replay, usually due to a network
timeout, a warning message will inform you that the End Event has been reset to
Automatic: Not Set Yet.

Replay the script to automatically assign the End Event or assign the End Event manually.

**Note:** You may need to replay the script several times until all steps have been accurately
synchronized