Agreed: it is very annoying to search for the single execution that met a specific criteria, i.e. got past the initial filters and ran through the entire workflow.
Because we don’t have access to the saved execution id in the workflow as it is running, there isn’t really a way to identify any particular execution.
It’s hard to debug a prior execution for workflows that happen with any degree of frequency.
edit:
I see, it’s an enterprise feature.