Forum Discussion

LStrike's avatar
LStrike
Copper Contributor
Jan 07, 2025

Azure Logic App - Scheduler is delayed but needs to run on a certain time

I have a workflow which should run every day at 6am, but on several days it is delayed up to 4 hours or sometimes more. And it is not, that the workflow is triggered at 6am and was on hold for 4 hours, it is, that the trigger itself was fired delayed.

I have an Azure Logic App in standard tier. Currently I have 10 Workflows deployed, some of them with Blob triggers, some of them with schedulers. At least one of the Workflows has a very high load of consumption. These high loads are usually between midnight and 1am.

I am aware, that if there is a workflow, which has a huge number of parallele instances, could affect other workflows.

But is there a chance, to make sure, that the scheduler is triggered at the right time? Is there an option, that a certain workflow could be prioritized?

The config of my scheduler is as followed:

{ "type": "Recurrence", "recurrence": { "interval": 1, "frequency": "Day", "timeZone": "W. Europe Standard Time", "schedule": { "hours": [ "6" ], "minutes": [ 0 ] }, "startTime": "2024-10-07T06:00:00Z" } }

In the trigger history I can see, that the scheduler was "fired" to late:

 

  • Kidd_Ip's avatar
    Kidd_Ip
    MVP
    Jan 08, 2025

    Consider below:

     

    1. Optimize High-Load Workflows: Since you mentioned that one of your workflows has a very high load of consumption, try to optimize or reschedule this workflow to run at a different time. This can help reduce the load on your Logic App environment during critical times.
    2. Dedicated Logic App for Critical Workflows: Consider creating a separate Logic App instance specifically for your critical workflows that need to run at precise times. This can help isolate them from other workflows that might cause delays.
    3. Increase Throughput: If you're using the Standard tier, you might want to look into increasing the throughput units for your Logic App. This can help handle higher loads more efficiently.
    4. Use Azure Functions: For more precise scheduling, you can use Azure Functions with a timer trigger. Azure Functions can provide more granular control over execution times and can be a good alternative for time-sensitive tasks.
    5. Monitor and Alert: Set up monitoring and alerts to track the performance of your Logic Apps. This can help you quickly identify and address any issues that might cause delays.
    6. Prioritize Workflows: While Azure Logic Apps don't have a built-in feature to prioritize workflows, you can manage the execution order by carefully scheduling your workflows and optimizing their performance.

Resources