Operations

Studio separates everyday content administration from database maintenance and account recovery. Operations requires its own access configuration. Changing a site mode does not itself modify a database.

Find an Operation

Task	Documentation
Choose initial, operational, maintenance, or recovery mode	Site Modes
Configure Operations access or upgrade a database	Maintenance & Recovery
Export and restore a Studio or Edge database	Backups & Restore
Recover an account or the last administrator	MFA Recovery
Repair a derived Post/Page search index	Content Search
Diagnose an API or resource failure	Operational Logs
Review major account, content, or maintenance actions	Audit Log

Database and Deployment Boundaries

Studio D1, Edge D1, and Media R2 are separate stores. Database backups do not contain R2 file bytes or Worker Secrets. An operation spanning both databases does not become one cross-database transaction.

A Worker rollback changes the code, not the database schema. If the entry screen reports DATABASE_NEWER_THAN_CODE, deploy code compatible with the stored schema and check the intended DB binding. Do not change a schema version value to bypass the check.

Studio database upgrades use the supported Operations workflow rather than manual SQL or Wrangler D1 migrations. Operations reports the stored schema and the version required by the running Worker; schema versions are independent of Studio’s package version.

Studio maintenance mode stops Studio product requests. To pause the separate public Edge Worker for database work, set its EDGE_MAINTENANCE_MODE=true. Neither operation automatically changes the other’s configuration.