Sounds like a plan. A lot of our community members have home-grown solutions for these kind of use-cases. In your case, since LP2 is dependent on LP1, you can store the data returned by the ETL workflow in a DB, and check if the data is available for a certain period of time. The check can be encapsulated in a task in your modelling workflow. You can also use FlyteRemote within your modelling workflow to check for the status of your ETL workflow, but not sure if that's a good way to go about. In a nutshell, the launch plan will be triggered daily irrespective of the status of your ETL workflow; you need to handle the verification part within your modelling workflow.