Microsoft
Microsoft@edwardyhe Based on our previous conversation with regards to the service errors for completion/deadlettering on Logic App standard, we have changed the Max burst/Max Instances/etc.
Again, our app service plan is shared for multiple Logic App Standards. On the plan we e.g. set 6 burst/instances and then for e.g. 3 LA standard we set active instances to 2 per LA standard.
We observed that the issues continue to happen on Dev, Test, Acceptance. When we delete the whole plan and Logic Apps and recreate them through the pipeline, it seems to stabilize. Start/Stop/restart of the app services do not seem to help.
It is a somewhat penible situation, because it means that each time we build a new logic app and deploy it (which means expanding the burst and max instances on the app service plan with X and set the ready instance of the LA to Y), it either will give issues on the scaling, or it might just work.
I believe that it will give issues, just as it does now. This would mean that we need to delete everything and redeploy each time we add a new integration. And we also need to manually keep track of the current max burst (and increase it in our devops libraries) + adding the new integration to it.
Is it expected from your side, that even when you set the numbers, this issue continues to occur? If not, do you have any advice or would it be possible to raise a ticket from my client perspective and plan a short meeting with you to see what is the best thing to do?
This is the message we're facing very often, leaving the Logic App in a running state until we manually cancel it.
{ "code": "ServiceProviderActionFailed", "message": "The service provider action failed with error code 'ServiceOperationContextUnavailable' and error message 'The call to retrieve the action context has timed out. This could be due to a scale-in event. Please try adjusting the auto-scale settings for this logic app to fix the number of active instances.'."}
