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 ?
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 ?
