Open robin-leach opened 1 year ago
We've deployed changes resolving the underlying issue. These changes are live as of 13:10 (BST) today and should prevent any future overlaps in MILS and MELS datasets.
Correcting historic data overlaps is a separate activity - we'll keep this issue open to track it.
Describe the issue
For MILS/MELS data with a notification time of between around 15:00 UTC on 08/06/2023 and around 14:45 UTC on 14/06/2023, the Insights API is returning responses with overlapping declarations.
Since the Insights frontend uses this API, the following frontend pages are also affected:
Steps to Reproduce
Steps to reproduce the behavior:
https://data.elexon.co.uk/bmrs/api/v1/datasets/MILS?from=2023-06-14T06%3A30Z&to=2023-06-14T07%3A00Z&bmUnit=2__BFLEX001
Similar behaviour can be seen for MELS here: https://data.elexon.co.uk/bmrs/api/v1/datasets/MELS?from=2023-06-14T02%3A00Z&to=2023-06-14T02%3A30Z&bmUnit=T_DRAXX-3
Expected behaviour
No overlaps are observed, as for each time period the most recent declaration is taken over all of the previous declaration.
Observed behaviour
Overlaps are observed as described in "Steps to Reproduce" above, without clarity as to which was the correct final MIL/MEL.
HTTP requests/responses
For the https://data.elexon.co.uk/bmrs/api/v1/datasets/MELS?from=2023-06-14T02%3A00Z&to=2023-06-14T02%3A30Z&bmUnit=T_DRAXX-3 example, this is the response body:
Checks
Please answer the following questions for yourself before submitting an issue.