Project randomly 503's after removing spending cap
I have a Pro project that had a spending cap of $25 on it. I noticed my app requests were timing out with context exceeded deadlines so I removed the spend cap. After restarting the database I'm still getting
503 Service Unavailable
503 Service Unavailable
responses about 50% of the time.
Is there a way to force refresh my project to abide by the new unlimited spending cap?
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.