Cloning functionality failures
Timeline · 2 updates
- investigating Jul 09, 2026, 01:31 PM UTC
Following our recent release, we identified an issue causing the cloning functionality to fail. All other core systems and features remain fully operational. To restore full cloning capabilities as quickly as possible, our engineering team will roll back your environment to the latest stable version. To avoid unexpected disruptions, the rollback will be performed during your standard deployment window. No action is required on your part, though cloning will remain unavailable until your specific maintenance window concludes. We will provide an update once the rollback is complete, or if new information becomes available. We sincerely apologize for the inconvenience and appreciate your patience while we work to restore full service.
- resolved Jul 10, 2026, 09:10 AM UTC
We have successfully rolled back the environment to the latest stable version during the scheduled deployment window. The issue impacting cloning has been resolved, and all cloning functionality is now fully operational. We monitor our systems closely following updates to ensure continued stability. If you experience any residual issues or have further questions, please do not hesitate to reach out to our support team. Thank you again for your patience and understanding while we resolved this matter.