Error! Logic App Standard Zip Deploy Creates Duplicate local.settings.json

Michael Liben 241 Reputation points
2025-04-02T17:34:46.9966667+00:00

This began yesterday, 01-Apr-2025. When we zip deploy our logic app standard workflows the Logic App stops working and we see Error in the Runtime version on the overview page. We tried restarting but error persisted. Not seeing anything obvious, we download the app content, opened up the zip file and immediately noticed two files named local.setting.json. One had the timestamp comparable to the other files and the other was four hours in the future, obviously using GMT which is currently four hours in the future.

Since we had both files in out downloaded zip and knew we could deploy, we went to the storage account hosting the web site and deleted the local.settings.json file. We restarted the Logic App and voila, it began working again.
We've been doing zip deploys for months and we first observed this behavior yesterday. We were able to repeat in another environment today with the same 'fix.'

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,456 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Khadeer Ali 4,795 Reputation points Microsoft External Staff
    2025-04-08T12:06:35.31+00:00

    @Michael Liben ,

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer .

    Issue: Error! Logic App Standard Zip Deploy Creates Duplicate local.settings.json

    Solution/Work Around Followed:

    I appreciate you confirming that removing the local.settings.json file post-deployment and restarting the Logic App worked as a temporary workaround. I'm glad to hear that your most recent deployment went smoothly without any issues.

    Moving forward, as discussed, manually excluding the local.settings.json file from the deployment package before performing a zip deploy is a recommended practice. This will help prevent unexpected runtime errors due to file duplication. Additionally, since you're not storing any secrets in the local.settings.json, this makes your deployment process even more streamlined and secure.

    Hope this helps. Do let us know if you have any further queries.



Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.