I believe that this is correct. Just bear in mind that as a mostly single-threaded and complex app with lots of async processing, assessing what order things get run in can be quite a challenge. Certainly in the earlier days of node-red though, we were told that the first tab would get executed first.
No, I don't believe so. But we would probably need confirmation from @knolleary.
In general, I believe that execution will happen in the order in which things are added to the flows file. But again, bearing in mind the caveat around async operations.
I think that any code in on start sections is executed when node-red initialises, I believe that would be before any of the flows start.
Excellent, thank you!
This is exactly the assertion I was looking for.
But I'm not sure I understood your second comment, Nick:
Does node-red finish initializing all the nodes (with their 'On Start' sections) before starting the messaging? (else initialized nodes may be sending messages to yet-uninitialized nodes)
No. There are not a separate 'initialise' and 'start' phases. Nodes just get started. The 'on start' code of a Function is nothing special in the lifecycle of the node - it is code that gets run when the node is started, rather than when the node receives a message.
Hence I will programmatically hold back unsolicited messages (e.g. auto-inject, incoming HTTP etc.) until I know their target nodes are ready (maybe set a flag in the rightmost tab).
Could be a nice feature request for the future - to enable global 'pre initialization' & 'post initialization' segments.