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

Loading... instead of edit #4225

Closed
lauracrouse opened this issue Feb 20, 2024 · 2 comments
Closed

Loading... instead of edit #4225

lauracrouse opened this issue Feb 20, 2024 · 2 comments

Comments

@lauracrouse
Copy link

lauracrouse commented Feb 20, 2024

Describe the Bug with repro steps

  1. Open the Logic App
  2. Create a new app
  3. Add the "When an HTTP request is received." trigger
  4. Click on the trigger to modfiy.

What type of Logic App Is this happening in?

Standard (Portal)

Are you using new designer or old designer

New Designer

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

Yes

Workflow JSON

{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "actions": {},
        "contentVersion": "1.0.0.0",
        "outputs": {},
        "triggers": {
            "When_a_HTTP_request_is_received": {
                "inputs": {
                    "method": "POST"
                },
                "kind": "Http",
                "type": "Request"
            }
        }
    },
    "kind": "Stateless"
}

Screenshots or Videos

image

image

Browser

Edge

Additional context

I found that I CAN edit it in the older version. This is definitely a bug!

@nidubey1
Copy link

Hi @takyyon , the Microsoft Support had been reached out with another customer issue facing similar error. In this scenario the issue occurs for any edit in any workflow where schema need to be provided such as parse JSON/Request trigger. Attaching the impacted workflow.json, and it is only occurring in the customer Logic Apps and not reproducible in our internal application. Session ID for the customer issue scenario: 29eab2613da540f384e3db4039e35f10
workflow 2.json

@hartra344 hartra344 assigned hartra344 and unassigned takyyon Mar 24, 2024
@hartra344
Copy link
Contributor

This was caused by us loading the Monaco editor(used for editing JSON and javascript actions like this) from the CDN rather than bundling it directly with the application. This works in most scenarios but does break if you're no a network that doesn't allow access to the CDN.
We have fixed this in #4401 , but it's took invasive of a change to hotfix. I'd advise using the old/fallback designer in the meantime if you can't access a more open network but it should be fixed in production in about a week or 2.

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

No branches or pull requests

4 participants