Missing Tracing Information
Missing Tracing Information Using the Synchronous Trace Analyzer
There are two possible reasons for not having any trace information:
Tracing has been disabled in the test case properties.
Tracing has been disabled on the corresponding service on the Bridge.
Solution: Enable Tracing in the Test Case Properties
The UML tab shows the following message:

Check the test case properties and tick the checkbox Enable Trace. Check the other trace settings whether they apply to your needs.
Run the test case again.
Solution: Enable Tracing on the Corresponding Service on the Bridge
The UML tab shows the following message:

Open a browser and switch to the administration interface of the corresponding Bridge. Check the xUML service preferences. Tick the checkbox Tracing Enabled and apply your changes.
Run the test case again.
Missing Tracing Information Using the Asynchronous Trace Analyzer
You clicked Show Available Traces in the content pane of the asynchronous Trace Analyzer, but no available traces were displayed.
There are three possible reasons for not having any trace information:
Tracing has not been activated on the asynchronous test definition.
Tracing has been disabled on the corresponding service on the Bridge.
The asynchronous trace has been triggered by a synchronous test case run, that collected the tracing information itself.
Solution: Activate Tracing on the Asynchronous Test Definition
Select the asynchronous test definition and click Read to read the actual tracing status of the service.
The Overview window displays the following in the asynchronous section:Click the Activate button.
Repeat your tests.
Solution: Enable Tracing on the Corresponding Service on the Bridge
The asynchronous Trace Analyzer shows trace as being active.
Open a browser and switch to the administration interface of the corresponding Bridge. Check the xUML service preferences. Tick the checkbox Tracing Enabled.
Repeat your tests.
Solution: Disable Tracing on the Used Test Case
Check the test case properties of the used test case of the corresponding WSDL and uncheck the checkbox Enable Trace.
Run the test case again.
Cannot Get Tracing Information Using the Asynchronous Trace Analyzer
You clicked Get Trace in the list of Available Traces on xUML Service but the trace could not be loaded.
Solution: The Trace File has Been Deleted due to the Retention Policy
The trace file could not be loaded because it has expired. You need to run the test case again to create new tracing information.
Expiration of Trace Files
Docker setup: Trace files expire after 7 days. After 7 days, the files are automatically removed from the file system.
Kubernetes setup: Trace files expire after 14 days. After 14 days, the files are automatically removed from MinIO.
The maximum storage space for tracing is 10 GB. If the 10 GB is exceeded, errors are reported.
The trace file retention time can be configured on your PAS instance. Please contact our support if you want to change the default configuration.
Related Pages:
Related Documentation: