Can I Renew Non-Renewable Instances in a One-Click Task After They Become Renewable?
No. The system renews only instances that could be renewed when a one-click renewal task is initiated.
If some instances support renewal but cannot be renewed when the task is initiated, for example, if they are in orders not yet paid, these instances will be considered non-renewable. Even if you handle the issue and these instances become renewable, they cannot be renewed in the task. To renew them, you need to cancel the one-click renewal task and then initiate a new one. Alternatively, you can manually renew these instances after the one-click renewal task is completed.
Example: If there was an unpaid order for an instance. You would not be able to renew it until the order was paid or canceled. If you initiate a one-click renewal task that includes an instance like this, when you confirm the renewal, the instance will be displayed with a non-renewable reason. After you complete the payment or cancel the order, the system will still not renew that instance.

If an instance is renewable when you create a one-click renewal task, but you later perform some operations like changing its specifications, the renewal may fail. This occurs because the system detects the change and prevents the renewal. To avoid such a renewal failure, you are advised not to manually renew, change, or unsubscribe from the instance if you have confirmed the renewal.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot