Logic App Standard | Insights | Runs - cannot [View] workflow run history or [Resubmit] due to errors

[darranhayes]

Describe the Bug

After enabling V2 app insights and end-to-end/distributed telemetry support with the following host.json settings in our Logic Apps Standard solution:

    "Runtime.ApplicationInsightTelemetryVersion": "v2",
    "Runtime.ApplicationInsights.PreserveIncomingOperationId": "true"

As described in this Azure Integration Services Blog:

https://techcommunity.microsoft.com/blog/integrationsonazureblog/application-insights-for-azure-logic-apps-standard---correlation-tracking-update/4132425

We cannot View Run History or Resubmit a workflow run from the Logic App | Insights | Runs view.

The cause of the problem appears to be that Insights uses the Operation Id as it's UI/navigation correlation id rather than the Run Id. When the above "PreserveIncomingOperationId" is set to false, the Operation Id appears to be the same value as the Run Id and therefore works as expected. See screenshots, log queries and output below.

However, when "PreserveIncomingOperationId" is set to true, the Operation Id is no longer the same value as the run id and this causes the UI to break for newly executed workflows.

Plan Type

Standard

Steps to Reproduce the Bug or Issue

1. Set host.json workflow value: "Runtime.ApplicationInsightTelemetryVersion": "v2"
2. Run a workflow
3. Go to Insights | Runs in the Azure Portal
4. Confirm that View and Resubmit workflow both work as expected.
5. Add to host.json workflow value "Runtime.ApplicationInsights.PreserveIncomingOperationId": "true"
6. Run the workflow again
7. Go to Insights | Runs in the Azure Portal
8. Confirm that View and Resubmit workflow still work for the previous workflow.
9. Confirm that View and Resubmit workflow does not work for the new workflow.
10. Observe the change in format of the Run Id column between the two workflow runs.

Workflow JSON

Screenshots or Videos

*1 host.json file:

*2 Insights | Runs showing incorrect and correct run ids:

*3 Logs query showing that the correct run id is always captured and that it is the operation id that changes:

*4 React error encountered when clicking [View] for the workflow:

Additional context

This issue appears to be a problem with the Insights blade within the Logic Apps portal and so may need to be raised on a different repo.

Also described here:

https://techcommunity.microsoft.com/blog/integrationsonazureblog/logic-apps-standard-monitoring-dashboards/4220065/replies/4475238