Logic App Trigger Time gets delayed one minute each day

Question

I am trying to understand why my Logic app does not start at hh:10, but it stats at hh:35 (after getting delayed almost a minute each day over several days).

According to the logic, it should run hh:10 every two hours.

     "recurrence": {  
                "frequency": "Hour",  
                "interval": 2,  
                "startTime": "**2022-06-27T14:10:00Z**",  
                "timeZone": "Pacific Standard Time"  
            },  
            "type": "ApiConnection"  

But, when I look at Run History, it runs around hh:35.

It appears that each day, it gets delayed by about one minute.

What is going on?

Answer 1

Hi @Anonymous

This trigger is a recurring connection-based trigger

In recurring connection-based triggers, such as Office 365 Outlook, the schedule isn't the only driver that controls execution. The time zone only determines the initial start time. Subsequent runs depend on the recurrence schedule, the last trigger execution, and other factors that might cause run times to drift or produce unexpected behavior, for example:

Whether the trigger accesses a server that has more data, which the trigger immediately tries to fetch.

• Any failures or retries that the trigger incurs.
• Latency during storage calls.
• Not maintaining the specified schedule when daylight saving time (DST) starts and ends.
• Other factors that can affect when the next run time happens.

For more information, review the following documentation:

• Schedule and run recurring automated tasks, processes, and workflows with Azure Logic Apps
• Troubleshooting recurrence issues

kind regards

Alistair Ross