Visual Studio Code Issue

[felipefernandezgomezkpmg]

Severity

P2 - High (Major functionality broken)

Describe the Bug with repro steps

Does this occur consistently?
Repro steps:

Action: startAllDesignTimeApis.startDesignTimeApi
Error type: Error
Error message: Timed out waiting for design-time startup for project "c:\Users\felipefernandez1\uaf-sandbox\workflows".
Correlation Id: 13B6C330-D0D4-4414-BCB7-AA3CD5789700
Session id: e2268259-ba43-4e88-a61b-f242cedd4ce61788534625714
Extension version: 5.996.0
Extension bundle version: 1.170.43
OS: win32 (Windows_NT 10.0.26100)
OS arch: x64
Product: Visual Studio Code
Product version: 1.136.1
UTC time: Fri, 04 Sep 2026 15:32:57 GMT

Settings

{
  "dataMapperVersion": 2,
  "validateFuncCoreTools": true,
  "autoRuntimeDependenciesPath": "C:\\Users\\felipefernandez1\\.azurelogicapps\\dependencies",
  "autoRuntimeDependenciesValidationAndInstallation": true,
  "parameterizeConnectionsInProjectLoad": true
}

Call Stack

waitForDesignTimeStartUp main.js:436125:5
async startDesignTimeApiInternal main.js:435939:7
async startDesignTimeApi main.js:435895:3
main.js:436264:7main.js:436264:7

What type of Logic App Is this happening in?

Standard (VSCode)

Are you experiencing a regression?

No response

Which operating system are you using?

Windows

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

No

Workflow JSON

Screenshots or Videos

No response

Environment

Version: 1.136.1 (user setup)
Commit: a44adf7f53e00964ab890f9f8758a334f1fc15bc
Date: 2026-09-03T05:06:41Z
Electron: 42.10.0
ElectronBuildId: 15109253
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
@github/copilot: 1.0.81-0
@github/copilot-sdk: 1.0.11
OS: Windows_NT x64 10.0.26100

Additional context

No response

[lambrianmsft]

felipefernandezgomezkpmg ,

We haven't made changes to the startup since the last version. If you install the previous version do you still encounter this issue?

[andrew-eldridge]

felipefernandezgomezkpmg this error was previously only logged to extension outputs but was recently changed to show an error message, there shouldn't be any other change in behavior. A couple of questions- (1) does the timeout occur consistently? (2) is this blocking any scenario that was previously working? Please provide any output logs as well

[github-actions]

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.