Posted Feb 1, 2026
Developed a Convex backend supporting web, mobile, and API for a CRM.
0
0

ctx.runQuery inside an HTTP action runs the exact same code as the real-time subscriptions. I'm not maintaining two implementations because the REST endpoint is just a thin wrapper around stuff that already exists.scheduler.runAfter, you know it works for one-off delayed functions. But when you need a chain for something like... "wait, then do X, then wait again, then do Y," suddenly you're managing state. What if step 2 fails? How do you know step 1 finished? How do you retry?fullName gets computed and stored. nextTaskDueAt gets copied from tasks to contacts. Writes get a bit messier. But queries stay fast, and I don't manage infrastructure.