MicrosoftHi DivSwa​ , re: Runs
When we enable logic app host.json settings to use the features described above and also enable correlated distributed tracing, the ability to view the run history or resubmit the workflow run is broken (navigating the entry marked with red lines in the second screenshot results in react render errors or failed attempts to resubmit). I believe this is because the runs table is using the operation id rather than run id as the correlating id for the UI action. The operation id that is used and propagated for tracing clearly changes with the enabling of PreserveIncomingOperationId and when I toggle this value between false/true, the subsequent runs can/cannot be navigated or resubmitted from the insights-runs table.
Which backlog can I raise this issue on? Or can this comment be passed on to the right team on my behalf. Thanks...
Screenshots included with some domain information such as workflow name masked out.
#1 Host file:
#2 Insights - Runs view showing incorrect and correct runids:
#3 Logs query showing that the correct run id is always captured and that it is the operation id that changes:
#4 React error that occurs when clicking 'view' in the Insights-Runs table. Also note that resubmissions fails also.
