Hi I am unable to change the idle period for an instance on Starter Plan and it’s set to 3900s. My guess is I had configured this before configuration of that was locked to Pro Plan? In any case I could probably recreate the service to get around it, but it’s used in a lot of places. I had to upgrade to an Xlarge instance size so effectively it’s running constantly at that idle period which is a big cost increase.
Hey! I’m taking a look at the issue
Thank you! here is the service id if it helps
70c42f56-e0d8-4ebb-9563-7c80d3c45734
Although to be honest this may be a very low priority as it sounds like I need to upgrade to Pro plan soon anyway with the Mistral acquisition.
Hi @noah_haibach , we’re currently working on fixing the issue and will circle back once it’s delivered, likely by tomorrow.
I just want to clarify that existing users and customers don’t have to take any action, you can keep using the platform as you’ve always been!
And @Michael_Merignargues and the team are working on fixing the issue you reported.
@noah_haibach , the issue has been fixed. You can now update the idle period from your service’s Scaling settings and redeploy. Feel free to reach out if you have any questions.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.