Skip to main content
The API, CLI and MCP return storage_jurisdiction_conflict with HTTP 409. Repeating the same request unchanged does not help.

What to do

Read ‘Storage jurisdiction’ in ‘ohmyhost project context —project ULID —json’ and set storage.jurisdiction in ohmyhost.yaml to that recorded value (us or eu). Existing R2 buckets and reservations keep their jurisdiction after a project-region migration; only new storage without a recorded bucket uses the project region. If context reports unavailable, report the request ID through feedback rather than guessing. Save or push the corrected version and plan its commit; for promotion, deploy it to Dev and promote again. Do not delete or recreate the project to move files. If the steps above do not resolve it, report it with the request_id from the error.