Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VS code: Taking longer time to load App service plan in logic apps tree. #2313

Closed
vgouth opened this issue May 10, 2023 · 10 comments
Closed

Comments

@vgouth
Copy link

vgouth commented May 10, 2023

Describe the Bug with repro steps

1.Create a new workflow app using VS Code.
2.Create a stateful/stateless workflow
3.Open the workflow.json file in designer and author a new workflow.
4.Save, debug and run it.
5.Create a logic app from logic apps tree
6.Expected: Should able to load create the logic app page in less than 5 minutes.
Actual: It is taking more than 15min minutes to load

What type of Logic App Is this happening in?

Standard (VSCode)

Are you using Preview Designer or GA Designer

Preview

Workflow JSON

No response

Screenshots or Videos

No response

Browser

VS code

Additional context

Artifacts Version:

  1. VS Code extension – vscode-azurelogicapps-2.15.15.vsix
  2. NuGet package: https://artprodeussu2.artifacts.visualstudio.com/A41bf5486-7392-4b7a-a7e3-a735c767e3b3/b32aa71e-8ed2-41b2-9d77-5bc261222004/_apis/artifact/cGlwZWxpbmVhcnRpZmFjdDovL21zYXp1cmUvcHJvamVjdElkL2IzMmFhNzFlLThlZDItNDFiMi05ZDc3LTViYzI2MTIyMjAwNC9idWlsZElkLzczMDA5ODA5L2FydGlmYWN0TmFtZS9kcm9wX2J1aWxkX0J1aWxkQXJ0aWZhY3RzX1dpbmRvd3M1/content?format=file&subPath=%2FMicrosoft.Azure.Workflows.WebJobs.Extension.1.21.3.nupkg
  3. Extension Bundle (CDN URL): https://cdnforlogicappsv2.blob.core.windows.net/logicapps-vendortesting
  4. Extension Bundle (Direct Download): https://cdnforlogicappsv2.blob.core.windows.net/logicapps-vendortesting/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows/1.21.3/Microsoft.Azure.Functions.ExtensionBundle.Workflows.1.21.3_any-any.zip

AB#24244432

@ccastrotrejo ccastrotrejo self-assigned this May 10, 2023
@ccastrotrejo
Copy link
Contributor

Yep, lets close it for now. There is this issue that we can use to track the work needed to solve this #2219

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants