@ajit more (PSP) Thanks for reaching here!
For Standard logic apps store all artifacts in an Azure storage account. During workflow creation and execution you might get the "Failed to save workflow." if these artifacts aren't accessible.
For example, the storage account itself might not be accessible, or the storage account is behind a firewall but no private endpoint is set up for the storage services to use.
To troubleshoot this
- Check the storage account's connectivity using Azure Storage Explorer.
- In your logic app resource's app settings, confirm the storage account's connection string in the appsettings, AzureWebJobsStorage and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING. If connectivity fails, check whether the Shared Access Signature (SAS) key in the connection string is the most recent.
If your storage account that's behind a firewall, check access to the storage account in the following ways:
- If firewall restrictions are enabled on the storage account, check whether private endpoints are set up for Blob, File, Table, and Queue storage services.
- Check the storage account's connectivity using Azure Storage Explorer.
For more details on troubleshooting suggest you refer this detailed document link- https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-diagnosing-failures?tabs=consumption#common-problems---standard-logic-apps
More information, review Deploy Standard logic app to a storage account behind a firewall using service or private endpoints.
Hope this helps. Let us know.