> ## 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.

# September 18, 2026

> New single setpoint ramping mode for virtual assets, FCR reserves on the operational data endpoint, automatic bid adjustment during unavailabilities, richer unavailability management in the webapp, and fixes for ancillary capacity release and monitoring graphs.

### New features

**New single setpoint ramping mode for virtual assets**

We have added a new ramping mode for virtual assets that ramps only at the start of a settlement period. This mode eliminates the path dependence of our existing ramping algorithm and does not require a draft schedule to be sent to the asset. This ramping mode also includes tolerant bounds that make it possible to schedule the full power of the asset. Schedules which are technically infeasible but within 50 kW of a tradeable quantity and the limits of the asset will be accepted. This is enabled automatically based on the asset's ramping mode when the virtual asset is created.

**FCR reserves on the operational data endpoint**

FCR reserves are now available through the operational data endpoint (and its latest-value variant). This exposes the reserve that the platform holds back for FCR as part of the state-of-energy boundary calculation, so you can see it directly alongside your other operational data categories.

### Improvements

**Automatic bid adjustment during unavailabilities**

For assets with fixed ancillary commitments, when an unavailability affects committed bids the platform now automatically adjusts or cancels the affected bids with the ancillary pool provider. FCR bids are made unavailable first, followed by aFRR bids in reverse merit order, so the least valuable capacity is given up first. This builds on the [bid unavailabilities](/changelog/2026/august/august-07) introduced on August 7.

**Richer unavailability management in the webapp**

We have continued to improve how unavailabilities are managed in the webapp. You can now mark an unavailability as excused and select an unavailability type, and review a read-only detail view with full change history and highlighted audit diffs. Availability tables have gained an explicit **View** action, separate from **Edit**, **End**, and **Delete**, and we have fixed several date and time picker issues when entering or editing periods.

### Bug fixes

* Rejected ancillary bids now more reliably release their capacity. Previously a rejected FCR bid could leave capacity tied up in the ancillary block instead of returning it to the wholesale block; the capacity is now released correctly.
* Fixed monitoring graphs so that Available Capacity and energy series no longer drift or comb when some minutes are missing — series are now aligned by timestamp.
* Resolved a bug in unavailability processing that could cause it to fail in certain cases, improving the reliability of how unavailabilities are applied.
