Debugging with the Flow debugger would be much faster if it cached the trigger for future runs.

Hello,

The use of the debug feature in Flow would be much more usable if it optionally cached the trigger data that it fetches the first time for subsequent runs. This would eliminate the need to have to reconfigure the setup for all the conditions to invoke the trigger, which depending on what the conditions are, can be time consuming, and is only relevant if it's the trigger itself that's being debugged - which is usually not the case..

Of course there are times when you'd want to disable the cached trigger in order to refresh the data for one reason or another, but most of the time, a single consistent cached set of data derived from a single triggered event should be fine to continue debugging with in most cases, and would save a lot of time when developing larger Flows.

Thanks,

Bryan