Obtaining fiber uris v3 concurrency

1. Automate Community
2. Tutorials & Examples

As yet another answer to HS's flow on this subject:
https://llamalab.com/automate/community/flows/44483

My other answers were ok for simpler flows, but having various subs created simultaneously makes it more difficult. The only solution I could find (so far, and I've left my other attempts as unconnected blocks for educational purposes) is to start every sub with a append log that would have something unique (a saved Now variable) so you can find the corresponding log entry for THIS fibre. This at the same time solves the issue of an ongoing log and therefore the same block id appearing ... This I think is the best solution until subroutine blocks also get fibre Uri outputs. It takes 2-3 blocks, one that appends the unique message to the log, another to read the log file. The third which is not necessary would be to assign the id to a variable. Not doing this would mean taking up more CPU and time extracting it eveytime. And the bigger the log gets the longer it will take most likely. So we will have to look into a way to clear/shrink the log without deleting other fiber logs that still need to be processed... And without adding tooany (extra) read write ops to log file, that might only mess it up, and certainly slow down and be resource consuming... So considering all of that I'm not sure it's a better solution to HS's...
If you have found any error or a better solution we'll be very happy to hear.