Marcus Nätteldal

Just wanted to mention that I've had the same problem where Error checking stoped working. Commented out the \ and it started working again. Tested on two different Windows clients.

> I found a workaround. I figured it out by opening up Microsoft.Azure.Workflows.Languages.Edge.JScript.Engines.dll and the class NodeProcessHandler. I found that out by increasing the log level for the func.exe by...

I managed to find a setting that did resolve this issue for me. Example structure: ``` root └─── LogicApps └─── LogicApp1 │ └─── Stateless │ workflow.json └─── LogicApp2 └─── Stateful...

Not working for me, also tried all the workarounds in this issue. Also, installing Azurite via NPM or some other source result in the same error. Worked the first time...

Ok got it to work... sort of. * Uninstalled Azurite (Extension) and Downloaded/installed from GitHub source. * Set the folder to C:\Users\\.azurite\ * Ran debug and it worked. * Edited...

That's not good, we're having the same setting however I've not tested that the intended behavior works as it should. "Runtime.Trigger.MaximumRunConcurrency: 10" Doesn't that setting allow up to 10 simultaneously...

I managed to find a setting that did resolve this issue for me. Example structure: ``` root └─── LogicApps └─── LogicApp1 │ └─── Stateless │ workflow.json └─── LogicApp2 └─── Stateful...

> This appears to be happening on a number of connectors at the moment within VS Code and looks to be due to something changed in the 1.0.34 version of...

If the logic app doesn't exist in the root project folder the designer will not work. A workaround is to add a project subpath in the settings file ``` root...

@san360 Have you been able to test my suggestion?