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

Cannot access logic apps (Internal Error) #4929

Closed
PRAGNYA-NR opened this issue Jun 3, 2024 · 14 comments · Fixed by #5422
Closed

Cannot access logic apps (Internal Error) #4929

PRAGNYA-NR opened this issue Jun 3, 2024 · 14 comments · Fixed by #5422
Assignees

Comments

@PRAGNYA-NR
Copy link

PRAGNYA-NR commented Jun 3, 2024

Describe the issue

  1. Go to visual studio code
  2. Sign into Azure
  3. create new logic app
  4. Cannot access it

vs_code_cannot_Access_iternal_error

internal_error_cannot_access_logic_App

image

Are you using new designer or old designer

New Designer (With action panels)

Screenshots or Videos

No response

Browser

vs code

Additional context

in Visual studio code

@PRAGNYA-NR PRAGNYA-NR added the a11y Accessibility label Jun 3, 2024
@hartra344 hartra344 removed the a11y Accessibility label Jun 5, 2024
@ccastrotrejo ccastrotrejo self-assigned this Jun 7, 2024
@ccastrotrejo
Copy link
Contributor

Hi @PRAGNYA-NR thank you so much for raising this issue. There is an ongoing internal email thread about this issue and the fix has been done on the backend side. Will close this issue and will update it once the fix has been deployed.

@ghost
Copy link

ghost commented Aug 14, 2024

@ccastrotrejo Any update on fix Release.
Thanks.

@ccastrotrejo
Copy link
Contributor

Hi @Krishna001223 this should be fixed by now. I tested it on some of our internal subscriptions and Logic Apps and it worked. Does still happens on your end? Is the defaultHostName property still being throwed?

@AzureDev0012
Copy link

Hi

We are also getting same error, but the logicapp has already few workflows deployed earlier. But not sure what happened we are unable to deploy from vs code now.
we can’t see any error, except “Could not resolve resource” message below the resource

@ccastrotrejo ccastrotrejo reopened this Aug 14, 2024
@ccastrotrejo
Copy link
Contributor

Ok, so I have re-open so we are aware of this happening again.
@AzureDev0012 what error do you see when you try to deploy to portal?

@ccastrotrejo
Copy link
Contributor

I can see some of our internal logic apps getting the same error. I will spend some time looking at these

@AzureDev0012
Copy link

We are not getting "deploy to logic app" option when right click on the Logic App.
Having only 3 options (Edit tags, refresh, Open in Portal)

Thanks

@ccastrotrejo
Copy link
Contributor

@AzureDev0012 yes, if the Could not resolve resource error its on the logic app, you might not be able to deploy to it.

@AzureDev0012
Copy link

@ccastrotrejo Is this because of configuration/ Application setting values?

@ccastrotrejo
Copy link
Contributor

Hi @AzureDev0012 not really. I just found the issue internally and will make a hotfix to resolve this.

@ccastrotrejo
Copy link
Contributor

@AzureDev0012 @PRAGNYA-NR A new extension version was released on Friday. This should fix that error

@wittysuyu
Copy link

wittysuyu commented Aug 20, 2024

Hi @ccastrotrejo, just would like to quick check if web app resource experiencing similar issue is related to the current bug?
image
image
image

If it is a separate issue, feel free to let me know and I will raise new thread.

@AzureDev0012
Copy link

@AzureDev0012 @PRAGNYA-NR A new extension version was released on Friday. This should fix that error

Thanks @ccastrotrejo It's working Now. Able to Deploy

@ccastrotrejo
Copy link
Contributor

Hi @wittysuyu might be related, however the App Services section its a different extension and codebase, you might need to reach out to them, or raise a Github issue on their side so they can resolve this. https://github.com/Microsoft/vscode-azureappservice

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

Successfully merging a pull request may close this issue.

5 participants