> ## 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. # October 16, 2026 > Turning on a new unavailability system with bid unavailabilities and unavailability events on the event API; better state of energy boundary handling; support for a wider range of physical asset grid connection arrangements; and improvements to day-ahead bids, partial FCR acceptance, and bid submission resilience. ### New features **A brand new unavailability system (opening up in sandbox)** We have built a brand new unavailability system. It is currently running in **dry-run mode**: this allows us to preview the revised impact of unavailabilities on ancillary bids, including how cancellations and adjustments on physical assets flow through to virtual assets, without enabling the full featureset. Over the next couple of weeks we will be opening it up for use in **sandbox**. **If you would like the new unavailability system turned on for your virtual assets in sandbox, please get in touch at [support@trlyr.com](mailto:support@trlyr.com) and we will set it up for you.** The new system introduces two things you will see through the API: * **Bid unavailabilities** — Sometimes an ancillary services bid can't be delivered *after* it has already been accepted by the TSO. In that case, besicherung (backup capacity provided by terralayr via our ancillary pool provider) is used for the unavailable volume. Each affected bid now carries an `unavailability`, where every entry has a `start`, an `end`, and a `volume`. The power you still have to deliver is the `acceptedCapacity` minus the `volume`. Reducing ancillary capacity is always a last resort: wholesale capacity is reduced first. See the API reference for [ancillary bids](https://docs.trlyr.com/virtual-assets-api-reference/ancillary/get-all-ancillary-bids-for-a-given-virtual-asset-and-interval.md) and [ancillary results](https://docs.trlyr.com/virtual-assets-api-reference/ancillary/get-all-ancillary-results-for-a-given-virtual-asset-and-interval.md). * **A new unavailability message on the events API** — The platform now publishes a new unavailability message to the events API. You can read it with [get events](https://docs.trlyr.com/organisations/\{organisationID}/virtual-assets/\{virtualAssetID}/events), where you can filter by event type with `types`, restrict the time window with `start` and `end`, and page and sort the results with `page`, `limit`, `sortBy`, and `sortOrder`. To see the effect of unavailabilities on your commitments and available capacity, request the `afrrPosCommitment`, `afrrNegCommitment`, `fcrCommitment`, `wholesalePowerCapacityChargeAvailable`, and `wholesalePowerCapacityDischargeAvailable` categories from the [operational data endpoint](https://docs.trlyr.com/organisations/\{organisationID}/virtual-assets/\{virtualAssetID}/operational). This builds on [bid unavailabilities in the API](https://docs.trlyr.com/changelog/2026/august/august-07.md), [automatic bid adjustment during unavailabilities](https://docs.trlyr.com/changelog/2026/september/september-18.md). For background on how unavailabilities behave today, see [Virtual asset unavailabilities](https://docs.trlyr.com/layrUserGuide/features/unavailabilities.md). **Support for a wider range of physical asset connection specifications** We have made a set of changes to ensure terralayr is ready for most types of Flexible Connection Agreement (FCA). Physical assets can now be supported with a much wider range of connection specifications, including **schedule freezes** and **external de-ratings** from their relevant DSO. External restrictions are now handled as operational data on physical assets. Use the `externalRestrictionMin` and `externalRestrictionMax` categories to set the lowest (charge-side) and highest (discharge-side) power an asset may run at, in signed kW where charge is negative and discharge is positive. These are sparse timeseries, so values only exist for the periods where you set a restriction. Asset scheduling now takes these restrictions into account together with the asset's internal state of energy bounds. ### Improvements **Better handling of state of energy boundaries on physical assets** We have improved how physical assets handle state of energy (SoE) boundaries. Projections on what the physical asset can deliver now respect the SoE boundaries, which allows us to better manage assets operationally and improves overall stability and availability of the virtual assets. **Day-ahead bids view in the webapp** The FCR and aFRR day-ahead bids view now shows when the bids were last updated and has a refresh control. Bids are sorted by capacity price and then by volume, so the most relevant bids appear first. **Partial FCR acceptance** When an FCR bid is only partially accepted, the front end now shows both the offered and the accepted volume in MW, and the graphs reflect the accepted volume. **More resilient bid submission** Submitting bids to the ancillary pool provider now retries automatically with exponential backoff when a transient error occurs. This makes our processing of ancillary services bids and results more resilient to pool provider instabilities. ### Bug fixes * Fixed the maximum total volume validation for ancillary bids so that it now takes already-accepted capacity into account. * Fixed a race condition when processing unavailabilities. Portfolio updates are now locked until they complete, so concurrent changes can no longer interfere with each other. * Fixed date and date-time inputs in the webapp so you can type a year without the field resetting. The year is also limited to four digits. * For portfolios of several assets, a failure to parse a single physical asset datapoint no longer blocks the remaining physical asset datapoints from being processed. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.