Logic App Standard fails to enumerate Workflows in Azure Portal

Hello John Dziurlaj,

This usually indicates a runtime/host issue inside the Logic App container, not necessarily a problem with your workflows themselves.

Please try below Options to resolve your issue.

Option 1:

1. Restart the Logic App (Most common fix)

Sometimes the Logic Apps runtime gets stuck.

Steps

Open your Logic App (Standard) resource.

Go to Overview.

Click Restart.

This restarts the underlying App Service host, which often resolves the workflow loading issue.

Option 2:

Verify WEBSITE_NODE_DEFAULT_VERSION

You mentioned upgrading:

WEBSITE_NODE_DEFAULT_VERSION = ~22

This may actually cause the problem.

Currently Logic Apps Standard runtime is tested mostly with Node 18 or 20.

Try changing to:

~18

or

~20

Steps:

Logic App → Configuration

Application settings

Update

WEBSITE_NODE_DEFAULT_VERSION = ~18

Restart the Logic App

Option 3:

Check the storage account

Logic Apps Standard requires a healthy storage account.

Go to:

Logic App → Configuration → Application Settings

Verify:

AzureWebJobsStorage

WEBSITE_CONTENTAZUREFILECONNECTIONSTRING

WEBSITE_CONTENTSHARE

If the storage account key changed or expired, workflows cannot load.

Option 4:

Clear portal cache (rare but possible)

Sometimes this is only a portal UI issue.

Try:

Hard refresh (Ctrl + F5)

Open in Incognito

Try another browser

Since you mentioned:

You upgraded Node version to ~22

The most probable issue is runtime incompatibility with Logic Apps Standard.

Recommended fix:

WEBSITE_NODE_DEFAULT_VERSION = ~18

Then restart the Logic App.

Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

The error indicates that the Logic Apps Standard host runtime cannot load the workflows, which commonly happens when the underlying storage (where the workflows and host files live) is unavailable or misconfigured.

Use the following checks and fixes, focusing on the storage account and runtime health:

1. Verify storage account and file share
   1. In the Azure portal, open the Logic App (Standard) resource.
   2. On the left menu, under Settings, select Environment variables.
   3. On the App settings tab, locate:
      • WEBSITE_CONTENTAZUREFILECONNECTIONSTRING
      • WEBSITE_CONTENTSHARE
   4. Confirm that:
      • The referenced storage account still exists.
      • The file share specified in WEBSITE_CONTENTSHARE exists.
      • There are no typos in either setting.
   5. In the portal, open the storage account and verify that firewall or network rules are not blocking access from the Logic App. If the storage account is behind a firewall, ensure private endpoints are configured for Blob/File/Table/Queue as required.
2. Check for common storage‑related runtime errors If the storage account is unreachable or misconfigured, the runtime can throw errors such as:
   • Access to C:\home\site\wwwroot\host.json denied
   • Network path not found for C:\home\data\Functions\secrets\Sentinels
   • Could not find part of the path C:\home\site\wwwroot
   • Encountered an error (ServiceUnavailable) from host runtime.
   These indicate that the runtime cannot read its configuration or workflow files from storage. Fixing the storage connectivity and settings resolves the issue.
3. Use Diagnose and solve problems
   1. In the Logic App (Standard) blade, select Diagnose and solve problems.
   2. Run the detectors:
      • Logic App Down or Reporting Errors
      • Network Troubleshooter
   3. Review the insights and follow any recommended actions, especially around storage connectivity and network configuration.
4. Validate network connectivity (if using private endpoints or restricted networks) If the Logic App is integrated with a virtual network and the storage account is behind a firewall:
   1. In the same virtual network, create a VM (can be in a different subnet).
   2. From that VM, test connectivity to the storage account using tools like nslookup for Blob/File/Table/Queue endpoints and Azure Storage Explorer.
   3. Resolve any DNS or connectivity issues found.
5. Restart the Logic App after fixing storage/network issues After correcting app settings or storage/network configuration, restart the Logic App from the Overview blade and then reopen Workflows → Workflows in the portal to confirm that the list loads correctly.

If the problem persists even after storage and network are confirmed healthy, use Diagnose and solve problems to gather more details and consider opening a support case with the runtime error information.

References:

• Deploy Standard logic apps to Azure storage that use private endpoints
• Troubleshoot and diagnose workflow failures in Azure Logic Apps
• Edit and manage logic app workflows in the Azure portal