# Demand-response exploration does not make every inference job interruptible

Finland's demand-response work was exploratory. Movable inference demand still requires a workload policy for deadlines, state preservation, restart and side effects.

Author: Retrivium editorial team
Language: en
Analysis published: 2026-11-03
Event date: 2026-09-09
Original announcement: https://blog.google/innovation-and-ai/infrastructure-and-cloud/global-network/clean-energy-finland/
Canonical URL: https://retrivium.ai/retrospectives/retro-finland-flexibility-compute/

Exploring demand response does not make every inference job interruptible. Finland's energy announcement describes flexibility work alongside supply development. The application's execution obligations remain a separate contract that an energy-planning statement cannot silently change.

## Earlier agreements addressed supply

The [October 14, 2024 Kairos agreement](https://blog.google/company-news/outreach-and-initiatives/sustainability/google-kairos-power-nuclear-energy-agreement/) concerned new nuclear development. The [October 27, 2025 Duane Arnold announcement](https://blog.google/feed/infrastructureduane-arnold-nuclear-plant-iowa/) concerned a planned restart. These supply-side precursors help explain the complementary role of demand timing. Developing generation and adjusting consumption address different parts of the system. One does not make the other unnecessary, and neither automatically defines which application work may be delayed.

## September kept flexibility exploratory

The [September 9, 2026 Finland post](https://blog.google/innovation-and-ai/infrastructure-and-cloud/global-network/clean-energy-finland/) described demand-response exploration within a portfolio that also included nuclear, wind and storage plans. Exploration is not a universal operating curtailment obligation. The source does not state that every model-serving request can be paused whenever grid conditions change. Its significance is an additional planning lever, with actual workload participation still needing its own operational design and conditions.

## Workloads have different timing contracts

An illustrative background evaluation can have a deadline that permits scheduling flexibility. An interactive request can have a different expectation. Even within background work, recoverability matters: stopping a process is not the same as preserving a usable checkpoint or avoiding duplicated output. These distinctions determine which work can move safely. They are application questions, not properties supplied by the presence of a battery or a firm-generation agreement in the same portfolio.

## A flexibility eligibility artifact

| Question | Why it matters |
| --- | --- |
| Can start time move? | Distinguishes scheduling from interruption |
| Can execution pause? | Identifies state-preservation needs |
| Can work restart? | Exposes repetition and side effects |
| What deadline remains? | Preserves the application's obligation |
| Who authorizes the change? | Connects energy action to service policy |

This illustrative artifact does not claim a Google operational procedure. It shows why useful flexibility is a qualified property of a workload. A job that can start later may still be unsafe to terminate after it starts. An apparently stateless worker can also have external side effects that require explicit handling before retry.

## The causal conclusion

The earlier supply commitments and Finland flexibility direction are complementary infrastructure levers. Their combination can support planning, but an application needs a defined execution policy before its capacity is treated as movable demand. [Inference routing and fallback](/journal/inference-routing-fallback/) explains recovery choices. [Reserve GPU capacity](/journal/reserve-gpu-capacity/) explains availability commitments. Together they preserve the distinction between an energy opportunity and an actual permission to delay, pause or repeat work under the service's existing obligations.