Missing Findings for Measurement Unit in Demo Instance

🐛 Bug Report

Summary

Validation for measurement units produced 0 Findings in the demo instance (2025-08-29), while the same dataset produced correct results (Compliance) in a later demo run (2025-09-01). It also produces correct results in the local instance.

Steps to Reproduce

Uncertain if the error is reproducable!

1. Run validation in the demo instance with a dataset containing measurement values, types, and units.
2. Scroll to the respective validation check in the generated report.
3. Compare results between different demo runs

What is the current bug behavior?

• Demo instance (2025-08-29): 0 Findings reported for measurement unit.
• Demo instance (2025-09-01): Correctly evaluated as Compliance.
• Local instance: Correctly evaluated as Compliance:

What is the expected correct behavior?

Validation should consistently evaluate presence of measurement unit as Compliance if correctly provided in all runs of the demo version

Relevant Logs, Screenshots, or Gifs

Demo instance (2025-08-29) - scroll to 8C: https://aqinda.gwdg.de/report/b562da52-0309-416a-b9b0-4bea7751d0b4/qpm Demo instance (2025-09-01): https://aqinda.gwdg.de/report/4ac7bf29-6b68-4817-94d0-e4d5d451784f/qpm Local instance - same constraints and almost the same data:

Environment Details

• Instance: Demo (affected in the first run), Local (not affected)
• Dataset: Kulturerbe Niedersachsen data in DDB

Additional Context

Likely a configuration issue in the demo instance rather than a QPM problem. Needs investigation of demo environment for consistency.