It sounds like you're experiencing unexpected trigger behavior in your Data Factory pipelines. This issue can occur due to various reasons such as incorrect trigger settings or overlapping schedules. Here are some steps you can take to troubleshoot this issue:
Check the trigger settings - Make sure that the trigger settings are configured correctly. Check the start time, end time, and the recurrence interval. Make sure that the trigger is not set to run immediately after being enabled.
Check overlapping schedules - If you have multiple triggers with overlapping schedules, this can cause unexpected behavior. Make sure that the triggers are not overlapping and that they are scheduled at different times.
Check the time zone settings - Make sure that the time zone settings for the trigger are configured correctly. If the time zone is set incorrectly, this can cause the trigger to run at the wrong time.
Check the pipeline settings - If the trigger is running the pipeline immediately after being enabled, check the pipeline settings to make sure that it is not set to run on-demand.
Check the logs - Check the Data Factory logs to see if there are any error messages or warning messages that might indicate the cause of the issue.
If none of the above steps solve the issue, you can try disabling the trigger and then re-enabling it after a few minutes. This can sometimes help to resolve the issue.
I hope this helps! Let me know if you have any further questions.