Skip to content

How to Fix Logic App Standard Runtime Version Error Quickly

solve logic app runtime version error

The “Runtime Version Error” in Logic Apps often appears unexpectedly. It can happen after a routine update or seemingly out of the blue. Diagnosing this issue requires a good grasp of the underlying Logic App Standard architecture, as its root causes are often tied to the job orchestration engine and Azure Storage dependencies.

In this article, we’ll break down common causes of the “Logic App Standard Runtime Version Error,” provide practical troubleshooting tips, and explain how to prevent future issues.

  1. Understanding the Logic App Standard Runtime Architecture
  2. Diagnosing Logic App Runtime Errors
  3. Check the Notifications Panel
  4. Use KUDU for Detailed Logs
  5. Verifying App Settings
  6. Checking the Installed Runtime Version
  7. Conclusion

Understanding the Logic App Standard Runtime Architecture

At the heart of every Logic App Standard is the concept of workflows. These workflows consist of actions processed as jobs by the runtime’s orchestration engine. The engine transforms workflows into directed acyclic graphs (DAGs), ensuring jobs are executed in the correct order while managing dependencies.

When a runtime error occurs, it’s important to understand how this engine handles workflow definitions, manages stateful and stateless jobs, and interacts with Azure Storage. Common failure points include:

  • Storage misconfigurations
  • Excessive retries from transient issues, such as HTTP 500 errors
  • Checkpoint failures caused by issues with state storage
  • Problems with the underlying host bundle or configuration
logic app standard runtime architecture

For more detailed information see here: Azure Logic Apps Running Anywhere – Runtime Deep Dive

Diagnosing Logic App Runtime Errors

Before diving into deep diagnostics, restart the Logic App Standard to ensure the issue isn’t temporary or due to outdated states. If this doesn’t resolve the issue, consider the following approaches:

Check the Notifications Panel

Microsoft has significantly improved the user experience by displaying errors in the Azure Portal’s notifications panel. Navigate to Notifications and look for error messages related to your Logic App. Keep in mind:

  • Notifications are not always real-time and may show resolved errors.
  • The panel might list errors that are unrelated to the current problem.
logic app standard runtime error notifications

Use KUDU for Detailed Logs

For more detailed insights, use KUDU to access runtime logs. Navigate to the CMD console in KUDU and locate the logs in: C:\home\LogFiles\Application\Functions\Host

Reviewing these logs often reveals the exact exceptions causing the runtime error.

Verifying App Settings

Logic App Standard relies on a storage account to manage queues, workflows, and runtime configuration. Misconfigured app settings or connectivity issues can lead to runtime errors. Verify the following key app settings:

  • AzureWebJobsStorage: Connection string for your Azure Storage account.
  • WEBSITE_CONTENTSHARE: Connection string for accessing workflow content.

Also, ensure the storage account is accessible:

  • Check private endpoint settings.
  • Verify firewall rules.

The error below indicates no host instance can be found, potentially due to network problems between the logic app and storage account, or a wrong connectionstring:

Request
[00b218c0-19c6-4bdb-80d3-72117c220da6] exception Azure.RequestFailedException:
No such host is known. (xsandboxdieter805b.blob.core.windows.net:443)
 ---> System.Net.Http.HttpRequestException: No such host is known.
(xsandboxdieter805b.blob.core.windows.net:443)

This typically indicates a connectivity or firewall issue preventing the Logic App from accessing the storage account:

Azure.RequestFailedException: No such host is known. (xandboxdieter805b.blob.core.windows.net:443)System.Private.CoreLib: Access to the path 'C:\\home\\site\\wwwroot\\host.json' is denied.

Checking the Installed Runtime Version

Runtime errors could also be related to a specific runtime version. In order to verify the installed runtime version. Use KUDU to inspect the deployed bundles:
C:\Program Files (x86)\FuncExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle.Workflows

logic app standard kudu installed workflow bundles

By default, Logic Apps use the following configuration, opting in for automatic updates of the Host Bundle Instance:

logic app standard jobhost extensionbundle version

Automatic updates are pushed by Microsoft per region, however, If automatic updates fail or cause issues, you can manually specify and force the logic app to use a specific host bundle version. In case a specific version hasn’t been installed yet, this will be downloaded first.

  {
    "name": "AzureFunctionsJobHost__extensionBundle__version",
    "value": "[1.91.14.0]",
    "slotSetting": false
  },

This type of error may require rolling back to a stable version and contacting Microsoft to report the issue:

Unable to resolve service for type 'Microsoft.Azure.Workflows.WebJobs.Extensions.Scale.SqlScaleMonitorService' while attempting to activate 'Microsoft.Azure.Workflows.WebJobs.Extensions.Initialization.WorkflowExtensionProvide'

Conclusion

Fixing Logic App Standard runtime errors often requires patience and a methodical approach. By understanding the architecture, leveraging diagnostic tools, and ensuring proper configuration, you can resolve most issues effectively.

Remember, prevention is just as important as resolution. Adopt best practices like regular monitoring, maintaining up-to-date configurations, and staying informed about runtime updates. With these skills, you’re well-equipped to handle runtime errors and keep your Logic Apps running smoothly.