Building (concatenation) debug messages, best practices (advanced flows)

Anyone got any good tips on how to build debug messages in a flow? I’m particularly interested in the following cases, but please add - I may not see all the possibilities.

Case 1: Concatenation
It would be awesome to print a debug message at the end of execution instead of several places in my flow. I would like to “document” how the flow actually progressed, and at the end print the whole track in one output (if possible).

Case 2: Execution time
Is it possible to extract the execution times for the flow? I think I’ve seen some script cutouts, but I cannot find them.

1 Like