Hello @Nitin Patil,
Could you please reduce the trigger time windows for testing purpose such as for every few minutes? let us see if that is not working?
If the trigger is not enabled, it will not run at the scheduled time, and I believe that you have already enabled it, right?
Check the trigger's dependencies. If the trigger has dependencies on other resources, such as a linked service or a pipeline, make sure that those resources are also configured correctly and are available at the scheduled time.
If someone has updated the Trigger at the time it was expected to run, then it will not trigger!!!
Mitigation
1. Change the trigger configuration
To have the trigger running as expected, the Status needs to be set as "Started". Hopefully we do this!
2. Setup Diagnostic
suggested to enable the Diagnostic to be able to monitor future occurrences because Diagnostics records who did the change by the user AAD Object ID.
Updated: 07/13
Glad to see the Triggers are running successfully, I would recommend to monitor them for the next run window?
They were supposed to run on 07/11/2023, but they ran on 07/12/2023.
Might be the window time is effective from the moment we update the trigger, please monitor for further!
I also noticed the timings for the two, which differed from the Eastern Time Zone, and I changed it to EST today morning.
It should not be different from what is set during creation of the Trigger, something might have changed in between. We can better monitor the trigger for further updates and we will for sure here to help if something is not right!
Please do let us know if we can close this case? Thanks for understanding!