Best practices for scheduling Admin updates on production sites
Last update: November 1, 2024
- Topics:
- Best Practices
CREATED FOR:
- Experienced
- Admin
- User
Schedule critical updates and operations on your Adobe Commerce sites during off-peak hours to prevent slow performance and outages on production sites.
Examples of critical actions:
- Admin configuration changes, for example updating a product attribute, or moving a product subcategory to another category
- Data import or export operations
Critical actions lead to cache invalidation and reindexing operations which significantly increase response time that can cause site outages.
Affected products and versions
- Adobe Commerce on cloud infrastructure
- Adobe Commerce on-premises
Additional information
Previous pageRespond to security incidents
Next pageUpdate services
Commerce
- Overview
- Architecture and integrations
- Maintenance and support
- Best practices
- Overview
- Planning
- Development
- Launch
- Maintenance
- Overview
- Post-launch support
- Audit frontend performance
- Optimize backend performance
- Indexer configuration
- Patching at scale
- Order processing
- Resolve database performance issues
- Respond to security incidents
- Scheduling Admin updates on production sites
- Update services
- Upgrade checklist
- Upgrade prerequisites for MariaDB
- Glossary
- Return to Operational Guides