Semantic Model Refresh just after the connected Dataflow Gen2 refresh

I want to submit an idea in the Fabric Community that we can have the refresh details of the upstream Dataflow Gen2 under the refresh setup settings in the semantic model. This can help set up the refresh of the semantic model immediately after the connected Dataflow Gen2 refresh. In small-scale setups, we can track the refresh manually, but in large-scale environments, tracking this becomes complicated. If the downstream semantic model refreshes 12 times while the Dataflow Gen2 refreshes only 6 times, we are wasting compute resources.