Intermittent Delay in Scheduled Logic App Trigger

Question

Intermittent Delay in Scheduled Logic App Trigger

Lu Li 31

Hi,

I'm using Standard Logic Apps, and I have a scheduled workflow that's set to run at 11 PM. However, I've noticed that on some occasions, it gets triggered around 4 AM instead. This issue happens intermittently.

I'm wondering if anyone else has experienced a similar problem?

Thanks,

Loknathsatyasaivarma Mahali 2,740 Reputation points Microsoft External Staff Moderator

2025-06-24T01:43:01.8233333+00:00

Hello Lu Li,

Thanks for reaching out, if your Standard Logic App with a scheduled trigger is running late (e.g., scheduled for 11 PM but runs at 4 AM), it’s often due to time zone misconfiguration or runtime behavior. First, ensure the recurrence trigger has the correct time zone explicitly set—by default, it uses UTC. Make sure Always On is enabled to prevent cold starts, which can delay execution. Avoid low-tier plans that may pause the app during inactivity. Additionally, check the Monitor tab for trigger delays and enable Application Insights or Log Analytics for diagnostics and alerting. For accurate and consistent scheduling, ensure both the Logic App trigger and hosting environment are time zone aligned and continuously running.

For your better understanding please refer to this Schedules for recurring triggers in Azure Logic Apps workflows, Schedule and run recurring workflows with the Recurrence trigger in Azure Logic Apps and Azure Logic App - Scheduler is delayed but needs to run on a certain time.

Could you please check the configuration based on the below screenshot. As per the screenshot it will Run at 11PM every day.

We would appreciate it if you could share the exact timestamp of the error and requested details via private message.

Here is the reference link on How to access & Data Privacy policy of private messages in Microsoft Q&A.
Lu Li 31 Reputation points

2025-06-24T04:32:44.8233333+00:00

Hi Loknathsatyasaivarma, thank you for your response.

This Logic App was originally deployed nearly 3 years ago, and the code has remained unchanged since then. Prior to this recent unexpected behavior, it had been running smoothly. As far as I can tell, it's using the correct time zone and an appropriate service plan (WS3), and I haven’t received any alerts related to this app. Below is the screenshot of the recurrence trigger.

Thanks,
Ripin 11 Reputation points

2025-06-24T15:17:14.9433333+00:00

Hi Lu Li, the recurrence configuration looks good. Can you please share the screenshot of the 'Run History' to verify any odd.
Loknathsatyasaivarma Mahali 2,740 Reputation points Microsoft External Staff Moderator

2025-06-26T01:06:06.57+00:00

Hello Lu Li,

I wanted to follow up to see if you have reviewed the previous message and the private message, and if you could provide the requested details to help us troubleshoot the issue.
Lu Li 31 Reputation points

2025-06-26T06:32:05.4133333+00:00

Hello,

Please see the screenshot below of the 'Run History'. The latest schedule was triggered nearly 5 hours later than the previous run.

Your answer

Loknathsatyasaivarma Mahali 2,740 Reputation points Microsoft External Staff Moderator

2025-06-24T01:43:01.8233333+00:00

Hello Lu Li,

Thanks for reaching out, if your Standard Logic App with a scheduled trigger is running late (e.g., scheduled for 11 PM but runs at 4 AM), it’s often due to time zone misconfiguration or runtime behavior. First, ensure the recurrence trigger has the correct time zone explicitly set—by default, it uses UTC. Make sure Always On is enabled to prevent cold starts, which can delay execution. Avoid low-tier plans that may pause the app during inactivity. Additionally, check the Monitor tab for trigger delays and enable Application Insights or Log Analytics for diagnostics and alerting. For accurate and consistent scheduling, ensure both the Logic App trigger and hosting environment are time zone aligned and continuously running.

For your better understanding please refer to this Schedules for recurring triggers in Azure Logic Apps workflows, Schedule and run recurring workflows with the Recurrence trigger in Azure Logic Apps and Azure Logic App - Scheduler is delayed but needs to run on a certain time.

Could you please check the configuration based on the below screenshot. As per the screenshot it will Run at 11PM every day.

We would appreciate it if you could share the exact timestamp of the error and requested details via private message.

Here is the reference link on How to access & Data Privacy policy of private messages in Microsoft Q&A.
Lu Li 31 Reputation points

2025-06-24T04:32:44.8233333+00:00

Hi Loknathsatyasaivarma, thank you for your response.

This Logic App was originally deployed nearly 3 years ago, and the code has remained unchanged since then. Prior to this recent unexpected behavior, it had been running smoothly. As far as I can tell, it's using the correct time zone and an appropriate service plan (WS3), and I haven’t received any alerts related to this app. Below is the screenshot of the recurrence trigger.

Thanks,
Ripin 11 Reputation points

2025-06-24T15:17:14.9433333+00:00

Hi Lu Li, the recurrence configuration looks good. Can you please share the screenshot of the 'Run History' to verify any odd.
Loknathsatyasaivarma Mahali 2,740 Reputation points Microsoft External Staff Moderator

2025-06-26T01:06:06.57+00:00

Hello Lu Li,

I wanted to follow up to see if you have reviewed the previous message and the private message, and if you could provide the requested details to help us troubleshoot the issue.
Lu Li 31 Reputation points

2025-06-26T06:32:05.4133333+00:00

Hello,

Please see the screenshot below of the 'Run History'. The latest schedule was triggered nearly 5 hours later than the previous run.

Share via

Intermittent Delay in Scheduled Logic App Trigger

Your answer