Azure Logic Apps Portal fails to display historical connector action details after API Connection replacement ("Unable to initialize operation details for swagger based operation")

[grajashekar-wcc]

Severity

P2 - High (Major functionality broken)

Describe the Bug with repro steps

Description:

Describe the bug

When an Azure Logic App (Consumption) uses the File System managed connector and the underlying API Connection is recreated or replaced, historical run history can no longer display the details of connector actions executed using the previous connection.

Instead of showing the action inputs, outputs and execution details, the Azure Portal displays an initialization error.

This makes troubleshooting historical failures impossible, even though the run history itself is still available.

Steps to Reproduce:

1. Create an Azure Logic App (Consumption).
2. Add a File System connector action (e.g. "List files in folder").
3. Execute the Logic App.
4. Cause one or more runs to fail.
5. Recreate or replace the File System API Connection.
6. Update the Logic App to use the new API Connection.
7. Open one of the historical failed runs.
8. Select the "List files in folder" action.

Actual Behaviour:

The Azure Portal cannot display the historical action details and shows the following error:

Unable to initialize operation details for swagger based operation 'List_files_in_folder'.

Error details:
Incomplete information for operation 'List_files_in_folder'.

The following information is no longer accessible:

• Inputs
• Outputs
• Error Details
• Raw execution payload
• Connector operation metadata

Expected Behaviour:

Historical Logic App runs should remain fully viewable regardless of whether the underlying File System API Connection has been recreated, reauthenticated or replaced.

Historical runs should behave as immutable execution snapshots.

The Azure Portal should display the action details captured at the time of execution rather than relying on the current connector metadata.

If the original connector metadata is unavailable, the portal should still display the raw execution inputs, outputs and error information instead of failing to initialise the operation details.

Impact:

This impacts production support and operational troubleshooting.

Recreating an API Connection is a common remediation step when resolving connector authentication or connectivity issues. After doing so, historical failed executions can no longer be inspected because the Azure Portal cannot render the connector action details.

This makes root cause analysis, incident investigation and auditing significantly more difficult.

Additional Information:

Observations:

• The Logic App executes successfully after switching to the new File System API Connection.
• The issue only affects historical runs that were executed using the previous API Connection.
• The Run History entry still exists and is accessible.
• Only the connector action details fail to render.
• This appears to be an Azure Portal rendering issue rather than a Logic App runtime issue.

Final Observation:

It appears that the Azure Portal attempts to resolve the current connector Swagger/OpenAPI definition instead of using the operation metadata that existed when the historical run was executed. As a result, replacing the API Connection causes the portal to lose the ability to render historical connector actions, even though the execution data itself should remain available.

What type of Logic App Is this happening in?

Consumption (Portal)

Are you experiencing a regression?

Not applicable

Which operating system are you using?

Windows

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

Yes

Workflow JSON

Screenshots or Videos

Environment

• Azure Service: Azure Logic Apps (Consumption)
• Azure Portal: Previous Logic Apps experience (Run History)
• Browser: Google Chrome (latest stable version)
• Operating System: Windows 11 Enterprise
• Connector: File System (Shared Managed Connector)
• Connector Type: Shared
• Connector Action: List files in folder
• Authentication: API Connection
• Logic App Trigger: Recurrence (Scheduled)
• Azure Region:

Additional context

This appears to be an Azure Portal/Logic Apps designer issue rather than a Logic App workflow issue.

Scenario:

1. The Logic App was using a File System API Connection.
2. The API Connection encountered an issue.
3. The connection was recreated/replaced and the Logic App updated to use the new API Connection.
4. New workflow executions complete successfully using the new connection.
5. However, historical failed runs can no longer display the connector action details.

When selecting the historical "List files in folder" action in Run History, the Azure Portal displays:

"Unable to initialize operation details for swagger based operation 'List_files_in_folder'. Error details - Incomplete information for operation 'List_files_in_folder'."

The action details cannot be viewed.

As a result, it is no longer possible to inspect:

• Inputs
• Outputs
• Error details
• Connector metadata
• Raw execution details

This significantly impacts production support and root cause analysis because historical failures become inaccessible after replacing an API Connection.

Expected behaviour:

Historical Logic App runs should remain fully viewable regardless of whether the underlying API Connection has been recreated, reauthenticated or replaced.

Historical executions should be immutable snapshots and should not depend on the current connector definition or Swagger metadata.

If the connector metadata is unavailable, the Azure Portal should still display the raw inputs, outputs and execution details captured at the time of execution rather than failing to initialise the operation details.