May 15, 2026

​

New features

• We have added the new data category deliveryPeriodSetpoint to the operational data endpoint (/organisations/{organisationID}/virtual-assets/{virtualAssetID}/blocks/{blockID}/operational). For ramp rated assets, this corresponds to the setpoint that the virtual asset ramps to during delivery, and can be different to the schedule value.

​

Bug fixes

• We have fixed how block capacity reservations are updated to account for the fallback scenario. Previously, if aFRR energy bids were rejected, the capacity would be freed up to allow for wholesale trading. Now, capacity is only freed up if there is no accepted aFRR capacity bid for that time. This is to handle the edge case where our Ancillary Services pool provider calls upon capacity market participants to provide aFRR, even if their energy market bid is rejected.
• We have corrected a bug in our schedule validation that could cause unavailabilities to be double-counted when computing the available power capacity boundary.
• We have fixed a bug in the state of charge calculation that could produce spurious zero values at timestamps where no energy measurement was present. The state of charge timeseries now omits periods with no underlying measurement rather than filling them with 0 automatically.