Closed CEardley closed 7 months ago
Thanks for raising this, we're looking into what's happened here and why this data is missing. Will keep this updated as we know more and have an idea of when this will be resolved. If there are any other acceptances that you know are missing from the datasets please do let us know.
@CEardley : Thank you for raising the issue. The team have identified the cause and have also followed up on the business rules wrt Acceptance numbers; this was an edge case as we did not foresee the same acceptance number for two different BMUs within the same Settlement Period.
This issue has been resolved internally, and has been for a while. We're now looking at backfilling any data we missed as a result of this bug (for example, the mentioned when the issue was first raised), and will close this issue once we have
This data has now been backfilled, and the data mentioned in the issue is now present at that endpoint. I'm going to go ahead and close this issue.
Describe the issue
BOAs are missing from BOALF endpoints. E.g., BOA 1193 for T_PINFB-3 on 2023-05-11.
Steps to Reproduce
Expected behaviour
Should return BOAs with acceptanceNumber = 1193 This BOA is seen in physical data on the Elexon platform https://www.bmreports.com/bmrs/?q=balancing/physicaldata (settlement period 8, 2023-05-11, T_PINFB-3) and detailed system price https://www.bmreports.com/bmrs/?q=balancing/detailprices (settlement period 8, 2023-05-11)
Observed behaviour
The below is the response from calling the URL listed above. Note 1193 for T_PINFB-3 is not present.
Screenshots
This screenshot is taken from the Physical Data page on BMRS for this BMU.
Additional context
T_PINFB-3 is one of 4 BMUs registered as part of the larger Capenhurst battery. BOA 1193 was issued to both T_PINFB-3 and T_PINFB-1 (as seen in detailed system price), however in the IRIS BOALF datasets it appears only for T_PINFB-1.
Checks
Please answer the following questions for yourself before submitting an issue.