Still unable to access app even after usage has been reset for the new month
Request usage unexpectedly spiked last month and the quota was used before I noticed, so I was unable to check the cause. I figured I'd just have to wait until the new month started which was in just a few days, but even now I'm still unable to access the app.
9 Replies
Hello atom,
If you navigate to the
Billing tab on the left side of your app list screen you can view where the request time by source came from.
You should always have editor access. Where does the clicking the app navigate you to?
As well in the billing tab you can view request time by
Triggers which will show you the actions using the most request time, in your case its the keepAlive action
Your keepAlive is running quite a lot, its enqueuing actions every couple of seconds which ran your request time to 200% of your hobby request time.Clicking the app was just throwing this error - I had no editor access
but now it seems to be resolved, as I can access it now
Yes somehow far too many recurring tasks got onto the queue. I've cleaned up the tasks so request time usage should be resolved now, but I will have to investigate exactly how that happened
It looks like the
keepAlive was enqueuing more frequently than intended. We do have an always-on add-on which would be more cost effective for this use caseSearching https://docs.gadget.dev/ yields no results for "always-on", could you provide a link to the relevent documentation please?
Unfortunately we do not have a page for it yet.
Ok well any insight you can offer about this
always-on add-on would be appreciated, since you think it would be a better fit for this use caseWith the pro-plan we have an optional add-on called
always-on which keeps your application always running by having 1 worker active at all times. Its an extra $25 a month on top of the pro-plan.