Supplied to the Dev team by Costas
Logging:
We need to be able to track flow runs (like Quickwork History), as well as what components were executed, variable values, etc. It is an essential part of all flow products and the only way to find out what exactly happened when it comes to support but also whilst developing and testing the flow.
There is another step in the debug feature still to be completed, so I have referenced this Idea within the story:
Debug Part 3: Show variable values overlayed on flow
Is it possible to return 'invalid json' blobs to the error log?
Related: Debug Part 2: As a flow developer I need to see trace information so I can understand what the flow is doing when I debug
This is different, but it's related: https://tenjin.ideas.aha.io/ideas/TJ-I-70
Due to security and GDPR...
When developing this we must make sure there is the ability to turn off the ability to store values, which could be the default setting, forcing people to turn it on for debug purposes.
I think this is especially important for HTTP actions as we currently can't tell why they go wrong which makes developing an HTTP flow harder