ST-2026-162 · Runtime & execution
Google Cloud Batch enforces same-region allowedLocations
Batch rejects new jobs whose allowedLocations places Compute Engine resources outside the job region from 31 July 2026, with a bounded 30 June 2027 exception for qualifying existing projects.
Previous state
A Batch job could specify allowedLocations regions or zones outside the job's own region.
Current state
Invalid cross-region allowedLocations causes job creation to fail under the applicable enforcement schedule.
Affected users
Who needs to care
Batch job definitions that populate allowedLocations with a different region from the job location.
Required response
What to do
Keep allowedLocations in the job region and audit qualifying older projects before their later enforcement date.
Evidence boundary
What the source does not prove
The 30 June 2027 date applies only to projects that successfully submitted a qualifying cross-region job before 31 July 2026; it is not a universal delay.
Lifecycle history
Dated event sequence
- Enforcement announced
Google published the cross-region constraint.
- General enforcement
All non-qualifying projects became subject to the constraint.
- Existing-project exception enforcement
Qualifying prior cross-region projects reach enforcement.
Evidence ledger
First-party sources
- 01Google Cloud — Google Cloud Batch release notes — allowedLocations enforcement
Official Batch release notes · 2026-07-20
Open official source ↗ - 02Google Cloud — Batch locations
Official Batch location contract · 2026-08-07
Open official source ↗ - 03Google Cloud — Batch jobs REST resource
Official Batch REST reference · 2026-08-07
Open official source ↗