LoadComplete shows this message if it cannot record requests to and responses from the tested web server. The most probable causes of this problem are the following:

No HTTP, HTTPS, SOAP, or WebSocket traffic has been sent during the recording session. For example, your web browser or client application was working in offline mode.
You are trying to record traffic sent via a protocol that LoadComplete does not support. Currently, LoadComplete can record only HTTP, HTTPS and SOAP requests and responses, and WebSocket messages.
You are trying to record traffic in the Firefox web browser that is not configured properly.
The server takes too long to respond and the response data has not been completely received when you stop recording.
The application whose traffic you are trying to record is added to the Ignore traffic of these applications list.
The domain, the traffic to which you are trying to record, is added to the Ignore traffic to these hosts list.
You configured LoadComplete to record traffic only from a specific application or to a specific host, but you used another application for recording or worked with another host.
In the Record User Scenario dialog, you commanded LoadComplete to use a specific browser for recording, but you used another browser.
If you use the specified browser, but the issue persists, it is possible that the antivirus or firewall software installed on your computer does not allow you to perform recording. To avoid the issue, you can do the following:
1. When you start recording, clear the Record traffic from this browser only check box.
2. In the Your settings differ from recommended one message, click Use your settings.
To avoid recording traffic generated by other HTTP clients running on your computer (for example, your email client or other web browser), you can use filters in LoadComplete.

No HTTP Traffic Has Been Recorded

See Also