Troubleshooting missing data in WATS

If you are new to WATS, and are struggling to find your uploaded data, here is a troubleshooting guide listing the most common reasons.

Date and Time

By default WATS filters are set up to show you the most recent data. This means that if you have uploaded data that is from tests performed more than 30 days ago it will not be visible.

System default is last 30 days, but you can alter your user default in the user settings.

Solution:

In your filter, alter the time period to encapsulate more time.

Other filter settings - Clear filter

Apart from the date and time filter, other filter settings might affect what is visible.

Solution:

Use the clear filter button to remove any filters.

Note that clearing the filter will also reset the time filter to your default. 

User access & restrictions

If your user is restricted, that might cause some data to be invisible.

In WATS, users can be restricted from seeing specific product groups or data from specific sites.

Solution:

Contact your WATS-account owner for details on your user access.

The reports never arrived on the WATS server

If data is missing, this can be caused by a problem at the station / client sending the test report.

In the WATS Control Panel > System & assets > System Manager you can locate your client and inspect the status, if files are being sent and any converters running with corrresponding errors:

WATS Client summary:

Converters and errors:

Quarantined reports

In some cases a report might appear on the WATS server, but have still violate some validation rule that makes it go into quarantine. This is most commonly related to time-issues and in many cases these reports will auto retry and be accepted at a later time. 

Solution:

You can find a list of quarantined reports in the control panel.

Processing delays

The report processing in WATS usually happens in a matter of seconds, but in some cases this processing might be slightly delayed - due to excessive workloads on the server.  

Solution:

Wait and retry

Units Tested More Than 100 Times

WATS is designed to optimize performance and resource usage when processing test data. If a unique unit—defined by a specific serial number (SN) and part number (PN) combination—is tested more than 100 times within the same process, it is excluded from statistical calculations and data warehouse aggregations.

This behavior is intentional. Units tested excessively can skew statistics and significantly increase the processing load. To maintain efficient query performance and reduce resource consumption, WATS:

• Stores the raw test data for these units without applying background processing.
• Skips statistical extraction and aggregation for such units.
• Excludes them from dashboards, reports, and filters that rely on aggregated data.

As a result, if your filters include a part number where all units exceed the 100-test threshold, no statistical data will appear—even though raw test records still exist.

Solution:

This is by design.

In some scenarios, you may include the unit's serial number in the filter to force a non-aggregated query.