Execution hours stuck at 500
Since the monthly limits refreshed from yesterday, the execution hours remaining were at 497 when I checked. Later in the day, it became 500 remaining and its still 500. I have just one service running (38f69c60-1cde-4567-89a9-5ed0f1e8a3f7). I believe this is messing with the cost estimation as well. My service is up and unaffected.
8 Replies
Project ID:
38f69c60-1cde-4567-89a9-5ed0f1e8a3f7why would you tell on yourself like this
you've unlocked the infinite hours glitch
Lol i need an estimate of how much this would cost to deploy for my org...otherwise i would happily not let anyone know π
ah I see
maybe just upgrade to the dev plan?
Yeah that's the plan cause my service is just a basic API and shouldn't go over the $5 monthly credit but wanted to confirm...
just wanting to tell you up front, if you are deploying for an organisation you need to be on the team plan
Ohh I see by org I meant my college... although this is not really official as in its handled by students only... A friend and I are trying to automate the process of registering for college events as a side project. Hence, the cost estimation was required for reimbursements if it does get approved
ah gotacha the dev plan is fine for the time it stays as a project between friends π