nibab
CCConvex Community
•Created by nibab on 4/30/2025 in #support-community
runAfter(0, ... timing
Hey! Im using runAfter to schedule a long-running operation (internal mutation) after a particular mutation is invoked (through an http api endpoint). What im seeing is that runAfter seems to be:
1. executing serially for all the invocations - ie im seeing the actions in runAfter being executed one after the other, never at the same time.
2. there is a significant delay between when i call runAfter(0, ..) and when the internal mutation gets executed.
Im trying to understand what my expectations should be here. What is the timing and the mechanics of runAfter ?
12 replies
CCConvex Community
•Created by nibab on 4/6/2025 in #support-community
Many bytes read in a single function ERROR on ctx.db.get() where no element exceeds 5000 bytes
Hey so ive got a strange warning on a simple function thats just getting elements with a ctx.db.get query. Im wondering if this has to do with the query being called a lot from a parent mutation, but then I would expect the warning to only be there for the parent mutation (which by the way also shows a warning).
The warnings are associated to the same request and the size of the element keeps going up, which again would make sense if the parent mutation is just piling on reads through this simple ctx.db.get...but my question is, why does the query get the warning too?
4 replies