Workflows disappeared from Logic App (Standard)

Question

I have set up an Azure Logic App (Standard) and Created 2 Workflows. The Logic App is configured using a static IP like described here:
https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/static-ip-of-logic-app-standard-using-nat-gateway/ba-p/3721443 Everything worked like it should until ~2 hours ago, but now - for unknown reason - the workflows aren't displayed anymore, although I haven't changed anything inbetween.
Sometimes (but not everytime) the following error is displayed:

Cannot reach host runtime. Error details, Code: 'BadRequest', Message: 'Encountered an error (InternalServerError) from host runtime.' 

Solutions referring to this error don't fit in my eyes, since i didn't change anything.
When i run diagnostics, i get some references to errors in my workflows,which may hiont that the workflows still exist - same do the logs in application insight.

How can i access my workflows again?

Answer 1

After one day all Workflows are displayed again.
We still changed nothing - so it must have been an error within Azure, but there was no notice about anything like that coming from MS - which is annoying.

Answer 2

I did run into the same error and after 2 days of debugging, I found the root cause and fixed my logic app alone. Let me share my experience with you for reference only. In my scenario, I had multiple workflows in the same logic app. While I was editing one of them, I suddenly 'lost' all workflows from Azure portal right after I received a workflow validation error, and the same error page (shown above). Please familiarize yourself with the built-in limitation of workflows especially the one for maximum depth (MaxDepth) of an action. My issue was caused by an incorrect schema template that I added to a Parse JSON action. Basically, it made Azure GUI unable to query the list of my workflows because of a single error in a single flow. Microsoft support recommended to rebuild the flow by cloning the content from workflow.json, which was nonsense and of course, it did not even fix the error but corrupted another, new logic app. So the only way to fix this was editing the workflow.json on the back-end (I use VS Code). This was the point when I started to use version control for my workflows.