I have a Logic App created to start my VM at 6am in the morning: The Logic App works, the VM does start. Why, though, does it take 1.5 hours to start? I can log into the VM a minute after the start time, so there doesn't appear to be an issue starting the VM on time. What is taking 1.5 hours? Anyone have an idea where to look?

In Microsoft's infinite need for more of our money in their coffers, they do not allow for adding a tech support ticket unless you sign up for their $30/ month support plan. No thanks. Then they funnel people to these community forums where I suppose such issues as mine go to die - ?

pflipper I've seen a similar issue in the past. There's probably an extension on the VM that's crashing, and the default timeout is 1.5 hours. I suggest you check if you have any extensions on that VM that are failed and if all are showing up fine you can try to re-install all of them and try again. If that doesn't help I suggest raising a case with Azure Support. They should be able to help you out.

I found one extension that failed - enablevmaccess. From what I read, that VM extension is used to reset the local password inside the VM and that since on a Domain Controller there is no "local" password to reset; the extension doesn't support VMs running as Domain Controllers. As such is the case, I just removed it. Let's see if that solves the issue. If so, you will be the winner of the "best response" contest I've been running here for the past month 🙂Back to your suggestion of raising a case with Azure Support... as I mentioned before, Microsoft does not allow for adding a tech support ticket unless you sign up for their $30/ month support plan. No thanks.

May be time zone issue. like timezone for login app is different than VM time zone

But I set it to start at 6am, then I get the success message at 7:30am. That would indicate that it does take 1.5 hours, not that there's a time zone change. The 1/2 hour would be hard to match up to a timezone issues as well.

Why does a VM take 1.5 hours to start? | Microsoft Community Hub

17 Replies

Vinoth_Azure
MCT
Oct 17, 2023
pflipper Please check the logic app retry policy and concurrency control policy, those two affect the long duration of the Logic app trigger.

Also please check is there any connection issue between the logic app and the virtual machine.

Thanks,
Vinoth_Azure.
- pflipper
  Copper Contributor
  Oct 17, 2023
  Vinoth_Azure
  
  Where is the logic app retry policy. I did a search and I am not finding it referenced on the logic app:
  
  I appreciate everyone's input, and a menu path for where you are suggesting to check items would be immensely helpful.
  
  Thanks!
  - Vinoth_Azure
    MCT
    Oct 19, 2023
    You can use following Microsoft article to under the retry policy settings,
    
    https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-exception-handling?tabs=consumption
Kidd_Ip
MVP
Oct 17, 2023
pflipper

So assume VM startup normal by manual, so any hints from event log that triggered by Logic App?
- pflipper
  Copper Contributor
  Oct 17, 2023
  Kidd_Ip -
  Are you talking about the Activity Log? I don't know what you mean by event log, otherwise. And there is nothing in the Activity Log (ignore the thing there that I just ran while looking for the event log).
  
  Giving me the menu path would help.
govindagoud
Copper Contributor
Oct 11, 2023
May be time zone issue. like timezone for login app is different than VM time zone
- pflipper
  Copper Contributor
  Oct 11, 2023
  But I set it to start at 6am, then I get the success message at 7:30am. That would indicate that it does take 1.5 hours, not that there's a time zone change. The 1/2 hour would be hard to match up to a timezone issues as well.

Forum Discussion

Why does a VM take 1.5 hours to start?

17 Replies

Resources