I implemented the automation scaling tool and it works as described. We can scale hosts up or down via the tool. The problem is when we look at the Logic Apps screen in Azure, we see page after page of entries still in the running state. When we look at the automation runbook, the job statistics are all green and completed. If we drill down into the list of jobs, they all say completed and have a green check mark. Somehow the Logic App is not learning of this and stays stuck running. Please advise how to correct this. There must me something missing in the scripts.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@ricvil Thanks for your feedback! We will investigate and update as appropriate.
@ChristianMontoya Can you please check and advice on this.
This is a known issue and is being investigated. As you have observed, this will not impact the scaling operations.
@ricvil As mentioned above this is a know issue and this should not impact the scaling operation. Can you confirm if the scaling is impacted due to this.
No impact on the actual operation. It is just unsettling to see page after page of running Logic Apps. Not sure if this has any cost implication also. After a few weeks I can imagine thousands of stuck apps as we would run the app as suggested (every 15 minutes).
@ricvil Thanks for responding with the details.
@RoopChevuri Can you share insights on the cost implications and any work around to get over this issue.
We are investigating the issue and will get back to the thread.
From: VikasPullagura-MSFT notifications@github.com
Sent: Wednesday, March 11, 2020, 20:42
To: MicrosoftDocs/azure-docs
Cc: Roop Kiran Chevuri; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Automation Logic App stuck on running state (#49746)
@ricvilhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fricvil&data=02%7C01%7C%7C38c794f3dafc4efcd31308d7c6376b3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637195813628637229&sdata=%2BnT5abVTkd9%2FRJo5%2FVI%2FFHUQDppmrY9tTZWEB2%2F5QnU%3D&reserved=0 Thanks for responding with the details.
@RoopChevurihttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FRoopChevuri&data=02%7C01%7C%7C38c794f3dafc4efcd31308d7c6376b3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637195813628647235&sdata=aTYjtPkhEsfFqo0kAl9bbuhEDJcW5PrEpMc3ALdNjxM%3D&reserved=0 Can you share insights on the cost implications and any work around to get over this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F49746%23issuecomment-597991053&data=02%7C01%7C%7C38c794f3dafc4efcd31308d7c6376b3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637195813628647235&sdata=3Yoya4W5lLqIIX1soxymTRDYg6HvnDmNeTFhMVKKOuw%3D&reserved=0, or unsubscribehttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGH6I2BN6FUR5SWWMDR3FDTRHBK27ANCNFSM4LD22UAA&data=02%7C01%7C%7C38c794f3dafc4efcd31308d7c6376b3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637195813628657246&sdata=CKLerQXTQnjc3azcuaujXGxvobjr%2FMzXKiMdL6xVhqw%3D&reserved=0.
You can replace the HTTP Webhook by a simple HTTP request in your Logic App. That works fine!
I having the same problem, the Logic app stuck on running state. No output at all. I wonder if this is actually working or is it a script issue.
@miketoupin I just tried @raymondd78 's recommendation and the LogicApp now shows a 'Succeeded' state and the Automation Account job appears to still run successfully as well.
Hi @miketoupin
Thank you for giving feedback, can you check the Automation account Runbook "Exception" and share with us exception details then we will check and assist you with resolved steps.
Thanks,
I might need to try Raymond78 option. @viswananadham-k, the exceptions is empty.
Using sinple HTTP request worked. Now the LogicApp closing properly after half a seccond. Now we only have to resolve why the scaling does not work. Thanks!
@geek2point0 / @miketoupin- could you talk through the steps needed to that? Looking to tidy my implementation up a bit and sounds like this would be a good step.
@townendk I used the Azure UI to do it. I added a parallel branch action, so I could compare side-by-side. I set it as a POST and just copied over the URI and Body fields, then deleted the HTTP Webhook.
Thanks @Raymond78, switching to HTTP worked for me too. I'm assuming the only difference is that it doesn't wait for the job to be successful before it shows as 'successful' like a webhook would?
@ChrisTav424 Yes all jobs show as succesfull. But as the logic app call's a webhook of a runbook you can check the status of the runbook.
+1, we are experiencing the same issue.
Having the same issue and scale out is not functioning.
eploymentUrl TenantGroupName UserName
------------- --------------- --------
https://rdbroker.wvd.microsoft.com Default Tenant Group Certificate
Starting WVD tenant hosts scale optimization: Current Date Time is: 03/26/2020 14:48:14
It is in peak hours now
Starting session hosts as needed based on current workloads.
Checking session host: LightWVD-0.adroot.azwestern.edu
of sessions: 6 and status: Available
Current number of running hosts:1
Current total number of user sessions: 6
Current available session capacity is: 4
Current available session capacity is less than demanded user sessions, starting session host
HostpoolName: LightUse, TotalRunningCores: 4 NumberOfRunningHosts: 1
End WVD tenant scale optimization.
Most helpful comment
You can replace the HTTP Webhook by a simple HTTP request in your Logic App. That works fine!