"non-primary branch calculation time is exceeded" despite 0 hour compute time
For my Neon project, I have a primary production branch, a non-primary test branch, no other branches, and I'm on the free plan.
Looking at my Branches in the Neon console, it looks like my hours were just reset today or yesterday - my production branch has 0.47h active time, and test branch has 0h active time.
However, when I try to connect to my test branch (easiest way is to click on Tables when viewing the branch in the Neon console), I get the error
Request failed: non-primary branch calculation time is exceeded. From my understanding of the new free-tier allowances, my primary branch should be always-available, and my test branch should get 20 hours per month. Is that correct? If so, this seems like a bug.9 Replies
helpful-purpleOP•2y ago
I should also add that I've been using the test branch for several months now, so I suspect the change is the result of the recent free tier pricing changes
xenial-black•2y ago
@Joel can you share the project ID?
helpful-purpleOP•2y ago
flat-mouse-940484xenial-black•2y ago
Thanks! I've shared it with the team. They're investigating if there's some calculation error in the free tier plans.
Identified a potential issue. Work in progress. Sorry about the trouble @Joel
(and thanks for reporting)
@Joel can you try now
I have temporarily adjusted a limit on your account. The patch will rollout later
helpful-purpleOP•2y ago
@ShinyPokemon works!
xenial-black•2y ago
Great! Have a good weekend
blank-aquamarine•2y ago
Hey Evan! No rush, but I think I'm experiencing this issue as well (project ID
wandering-resonance-516513 if it's helpful). Do you know if the patch will rollout before the standard Friday release? Have a good weekend!adverse-sapphire•2y ago
Hi, I seem to be having the same problem with accessing branches other than the primary one. My project (with ID
rapid-meadow-47442358) is also on the free tier, so we're wondering when the fix will roll out? Thanks in advance 😀xenial-black•2y ago
@stock I see that the fix has been merged. Checking with engineering to determine if it's live.
@luguentz_malort CC