> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trlyr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# August 7, 2026

> Bid unavailabilities are now returned on the public ancillary bids endpoint, the frozen energy system is now the only unavailability system, plus protected schedule and frontend memory fixes.

### New features

**Bid unavailabilities in the ancillary bids response**

The public ancillary bids and results endpoints now return an `unavailabilities` array on each bid. These are recorded against bids that cannot be cancelled once an unavailability comes in. For example, if an unavailability appears after gate closure and we need to invoke backup capacity, we register a bid unavailability against the affected bid. Each entry includes the `start`, `end`, and `volume` affected, so you can see exactly which part of a bid was impacted and when.

```json theme={null}
{
  "deliveryDay": "2026-08-05",
  "product": "NEGPOS_00_04",
  "market": "FCR",
  "bids": [
    {
      "bidID": "caa630e8-0591-4cc4-ab72-762504c992b7",
      "capacityPrice": 1000,
      "energyPrice": null,
      "offeredCapacity": 1000,
      "status": "submitted",
      "unavailabilities": [
        {
          "start": "2026-08-04T22:00:00Z",
          "end": "2026-08-04T23:00:00Z",
          "volume": 1000
        }
      ]
    }
  ]
}
```

### Improvements

**Frozen energy is now the only unavailability system**

The frozen energy system [rolled out on April 24th](/changelog/2026/april/april-24) is now the only system we use. The previous unavailability system has been completely removed and all virtual assets have been migrated to frozen energy. The associated feature flag has also been removed, so there is nothing to enable — all assets now benefit from consistent energy handling during unavailabilities.

### Bug fixes

* Fixed incorrect adjustments to the protected schedule within the frozen energy system. The protected schedule is now only adjusted during the protected interval, and only deliverable power is truncated.
* Fixed a memory leak in the webapp that could cause browser memory usage to grow while the tab was left in the background.

We have also made a range of background stability improvements to how virtual assets are handled under unavailabilities. These are not directly customer facing but improve the resilience of the platform you rely on.