Flows started on second render pass are ignored

[Maciej Walusiak]

I have a case, where I fetch user from API on root application component, and once it is done, and this users mets certain criteria, children component is rendered on second rendering pass running it's own flow. This second flow is ignored by Arboris, which results in second flow to being called twice - once on a node server, then from a client browser.