Confusing error message while retrieving dataset with different schema version than stored one

Pawel Bartkowiak
2026-03-19T14:05:57Z

How to reproduce:

1. Choose analysis type with 2 supported schema versions, for example slimtube
2. Post data in schema version 2.0.0 (schema version defined at Accept header)
3. Try to retrieve data with schema version 1.0.0 in header
4. As a result following error appears:

`{`

`    "code": 400,`

`    "reason": "Invalid schema version has been provided. Schema version 1.0.0 is not one of proper versions: {'2.0.0'}"`

`}`

Error message is not accurate and might be confusing.

More meaningful would be one of following propositions:

* Schema version mismatch: this dataset is stored as schema version 2.0.0, but the request asked for 1.0.0.
* Invalid schema version has been provided: this dataset is stored as schema version 2.0.0, but the request asked for 1.0.0.
* Schema version mismatch for dataset \<id\>: requested 1.0.0, stored 2.0.0.