At WoodWing, we regularly maintain and enhance our Software as a Service (SaaS) offering to ensure you always have access to the latest features, improvements, and security enhancements to provide you with a reliable and up-to-date service.
Minimizing Disruption
WoodWing utilizes one or more of the following approaches depending on the product and/or service:
- Predefined maintenance windows
- Zero-downtime deployment techniques
- Emergency maintenance windows
These approaches help minimize the impact on your service availability. In rare cases where availability may be affected, you'll receive advance notification through the WoodWing Cloud announcement section.
Regular Maintenance and Updates
- Critical bug fixes, operational updates and security fixes are deployed at any time to maintain the highest level of security and ensure business continuity.
- Necessary operational updates and configuration changes are deployed as needed during standard maintenance windows.
Important: Standard maintenance window: 3 AM - 6 AM in your hosting region's timezone
Product Update Frequency
Updates planned during standard maintenance windows
-
Studio Web Client and Studio Server
Every 2 months -
Assets v6
Quarterly
Info: For more details on specific dates, please refer to the release calendar.
Note: Custom upgrade requests to an unplanned version or at a time outside the regular update schedule require a Statement of Work.
Continuous updates
- Assets v10
- WoodWing services (e.g., ECS (Enterprise Cloud Services), WoodWing Connect, and Identity Service)
Updates planned in agreement with customers
-
WoodWing Cloud-hosted InDesign Server
Updates are performed on request to align with the customer's Adobe client product updates. WoodWing supports the latest 3 versions of InDesign Server.
Dev, Test & Sandbox Update Planning
For customers that have a Dev, Test, or Sandbox environment of Studio Server and/or Assets 6, these upgrades are planned 2 weeks before the Production environment upgrades. Customers are notified of the upgrade planning through an announcement in the helpcenter. This schedule ensures that customers have time to run (automated) tests to ensure that integrations and workflows function as expected before upgrading their production environments. It is the customer’s responsibility to test and to report any critical issues before a planned production upgrade. If a critical issue is found and reported, the production upgrade will be paused until we can provide a fix for the issue.
Note: Studio Web Client is excluded from this release cadence.
Assets 6: Special Considerations for Large Asset Libraries
Upgrades to Assets can, in some cases, cause a re-index of the datastore. For customers with large asset collections, the re-indexing process may exceed our standard 3-hour maintenance window. In these cases:
- We will work directly with you to schedule the upgrade and re-indexing at a time that minimizes disruption to your business operations.
- Our dedicated technical team will be on standby throughout your scheduled upgrade window.
- We maintain complete backups of your current system that can be restored if needed.
Tip: For optimal performance, we recommend temporarily disabling access to Studio and Assets during the extended maintenance window to prevent user errors when deleting or moving objects. You can request this when planning the re-index. If access is disabled, users should be notified in advance of the planned downtime.
Re-indexing Options
If re-indexing extends beyond the planned window, we offer flexible approaches:
- Pause re-indexing during business hours to maintain normal performance (users may encounter occasional errors when deleting/moving objects).
- Continue re-indexing to complete the process more quickly, with some temporary impact on system performance.
In all scenarios, our team actively monitors your system and takes immediate action if any significant performance issues arise.
Comments
0 comments