The key output order is request accepted -> hash ready. Node can offload work, but your callback still waits for the event loop to pick it up.
A Node callback, timer, I/O task, stream, or worker-pool job runs later than expected. This matters for password hashing, image processing, filesystem bursts, DNS, and API latency under load.
Assuming async Node APIs never compete for limited worker threads.
Separate sync work, microtasks, timers, I/O, check callbacks, and worker-pool work in your mental model.
setImmediate(runAfterIO); // Avoid long nextTick loops that starve other phases.
The console lane proves the visible order: request accepted -> hash ready. The active line and queues show why source order changed.
Add timestamps around callbacks and inspect Node diagnostics, logs, or profiler output to confirm the runtime phase that is delaying work.
Related cases
Continue with nearby confusion while the mental model is fresh.
process.nextTick vs Promise
This matters in Node libraries, stream internals, CLIs, and tests that mix nextTick with promises.
setImmediate after I/O
This appears in servers, CLIs, file watchers, and test suites that schedule follow-up work after I/O.
EventEmitter listeners are sync
This explains surprising stack traces and error timing in Express apps, streams, queues, and internal event buses.
Was this clear?
This stays local for now. It helps you track where the product still needs sharper cases.