You can try Table Update Trigger (TUT).

So your pipeline2 will get triggered when there is an "update" to some chosen tables(s) updated in your pipeline1.

https://docs.databricks.com/aws/en/jobs/trigger-table-update

@Anish_2 - TUT is the solution. in TUT, instead of the parent pipeline "pushing" a notification, the child job is "pulled" into action by a metadata change.

Set it up as below.

1. Create a Databricks Job and add a Pipeline task pointing to your Secondary DLT pipeline.

2. In the Job settings panel on the right, click Add trigger.

3. Choose the Table update trigger type.

4. Point it to the specific Unity Catalog table generated by your parent DLT pipeline.

5. Set Sensitivity: Configure a "Minimum time between triggers" to ensure that if the parent pipeline updates the table multiple times in a short window, the child pipeline doesn't restart unnecessarily.

Hope it will give you the desired behaviour.