Are NocoBase 2.x workflows really "sequential"? I measured it, and everything ran in parallel

Short summary

An empirical investigation revealing that NocoBase 2.x workflows run in parallel despite documentation suggesting sequential execution. The author tested three scenarios — parallel branches with delays, CPU-bound JavaScript nodes, and concurrent workflow triggers — and found all execute concurrently. JavaScript nodes run in worker_threads, escaping the Node.js single-thread limitation, and parked executions yield the dispatch slot for others to start.

• •NocoBase parallel branches execute concurrently, not sequentially as docs imply
• •JavaScript workflow nodes run in worker_threads, so CPU-bound work overlaps too
• •Multiple simultaneously triggered workflows run in parallel with ~70ms startup spread

Generated with AI, which can make mistakes.