@Benoit Chabord thanks for sharing this use case - it’s awesome to discover what people are doing with 2.0.
One pattern we would suggest is to use the dashboard filters to filter out the “checking” flow’s noise and create a view that only includes your “processing” flow.
However, I’m also noting your desire to see confirmation that the “processing” flow was kicked off and affirmatively decided not to do work (similar to Prefect 1.0's skipped state). We have a couple thoughts there, let me explore a bit. High level, Prefect 2.0 supports custom user states (e.g. you could create a “Skipped” state yourself) but the UI doesn’t show them in a special way, so it’s not especially useful at the moment. We’ll start working on the right way to advance that story.