__root__root beforeLoad calls the server function that returns the token and then calls serverHTTPClient.setAuth(token)serverHTTPClient.setAuth(token), so the convexClient has the token when the first convex functions are called, but the user isn't set yet on the convex backend. So the functions throw when they find no auth user (I see the "Not authenticated" errors in the convex dev server console) and that errors out the SSR with a message like the one below showing up in the web server console and the browser when the page loads. So there is a big delay between when the token is retrieved and processed in the serverFunction and when the convex server actually sets the user for auth.getUserIdentity()auth.getUserIdentity(). I feel like the convex auth with clerk is a black box to me, and I also feel like the authentication on the convex server needs to be triggered in that before load somehow.Hi @everyone! You asked and we delivered. Actions in the Convex runtime can now run for up to 30 minutes. All deployments are automatically opted in and this doesn't require any additional configuration. Docs: https://docs.convex.dev/production/state/limits#execution-time-and-scheduling
Jordan22 · 3d ago
Usage limits are now live! Set warning or disable limits on any individual deployment, so your vibe-coded app can't quietly burn through your paycheck. Pick a metric (function calls, database bandwidth, compute, egress…), a window (daily / monthly), and what happens when it's hit: get warned, or auto-disable the deployment before your credit card does. Set them per deployment in the dashboard. Docs: https://docs.convex.dev/production/usage-limits
chunkyboi · 5d ago
Dashboard got a little love this week! Check out the brand new Schema page for a visual representation of your table relationships
ari · 2w ago
Join the Discord to ask follow-up questions and connect with the community