Inputs - Outputs don't show proper error when debug mode is disabled for stateless workflows

Squarepour commented 8 months ago

Describe the Bug with repro steps

The following occurs on both Old and New designer:

Open Logic App workflow run history.

Click on any instance (success or failure).

Click on any Action.

Flyout pane on right appears, but Input and Outputs show "Error loading Inputs" or "Error loading Outputs", respectively.

Click on Show Raw Inputs (or outputs).

Details screen says Failed To Fetch and shows a URL. When I open the URL I see the following:

{"error":{"code":"InternalServerError","message":"Encountered internal server error. The tracking Id is 'REDACTED'."}}

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

No response

Screenshots or Videos

No response

Browser

Chrome Version 119.0.6045.160 (Official Build) (64-bit)

Additional context

I've been tinkering with these Azure logic apps for a few months and I've never seen an input or output populate from the run history log/view, ever. I'm struggling with my latest instance and really need to see what's happening here.

Remediation steps I've attempted so far (to no avail):

Add "https://portal.azure.com" to CORS allowed origins list.
Removed everything from CORS and input *, alone.
Adding the external IP of my work environment (AVD) to the Networking > Access Restrictions whitelist
Set up private endpoint connection to my work environment (AVD) within Networking > Private Endpoint connections
Viewing from a different browser (Edge)

If anyone has any insight, I'd really appreciate it. Also, please note that I did search for this and could not find anything. If I missed a closed or open case on this, apologies in advance.

AB#25912298

AB#26008841

Eric-B-Wu commented 7 months ago

Hi @Squarepour, thanks for reporting this issue, if possible can you follow the steps here under

https://purple-pebble-0e11de71e.1.azurestaticapps.net/tsg#collecting-console-errors
https://purple-pebble-0e11de71e.1.azurestaticapps.net/tsg#collecting-network-logs-in-a-har-file and send those details to wue@microsoft.com, with logs/network traces, it'll help us determine what is causing inputs/outputs not to load for you

Squarepour commented 7 months ago

Just sent the email. Thank you for your help!

Eric-B-Wu commented 7 months ago

followed up on email, doesn't seem like a UX issue, but might be a networking/functions issue - asked to create a support ticket so that support engineer can follow up on this

Squarepour commented 7 months ago

OK, we have a solution from the MS support team. This is so simple that I can't believe it had to go this far. Apparently, when editing a stateless Workflow, the workflow main page has a button on top "Enable debug mode". Image attached.

If I may suggest an update to the UX: please update the run history Input/Output fields to say "Error: Debug Mode currently disabled" instead of "Error loading inputs". There were zero breadcrumbs leading to the simple solution here.

In fact, there's probably an opportunity to save on load times when viewing Run History. The below "loading" fields take about 10 seconds to finally error out. If debug mode is not enabled, the loading shouldn't even be attempted.

hartra344 commented 7 months ago

@squarepour thanks for sharing what your problem was. I agree the UX around this could and should be better. Adding it back to our backlog.