Improve resubmit from an operational perspective
The resubmit feature is very powerful from a runtime perspective, but it can be improved from an operational point of view. It would be nice to have visibility on the resubmit, so that you know as an operator that specific failed workflows can be ignored, because they were resubmitted already. This can be achieved by adding an additional workflow status: Resubmitted. Another alternative solution is allowing an operator to query for failed Logic App run that were not resubmitted yet.
Thanks for your suggestion.
Lundqvist Christoffer X (SEIT) commented
Would be nice to have the feature to be able to select all and not just click one by one in Logic Apps Management, say you have +1000 will take very long time to select them one by one.
Also expand just not have the last 10 000 runs but be able to show more runs.
Sumit Kumar (Microsoft) commented
We have added bulk-resubmit feature in the Logic Apps Management solution for Log Analytics (OMS): https://blogs.msdn.microsoft.com/logicapps/2017/11/07/logic-apps-management-solution-updated-search-runs-by-tracked-properties-bulk-re-submit-and-more/
It would be nice if we are able to reprocess the Logic app Instances using powershell ... Not sure if already is in place
I have 2 Logic Apps, one is a parent Logic App which takes SQL records and the second one splits them(used split on) and call a web service.
now, I have got 1k Logic App instances has failed because the Webservices wasn't available. whats the best way to reprocess all the instances batch by batch ?
Klas A commented
As an additional suggestion, it would be great if the two workflow runs (resubmitting/resubmitted) kept references to each other in the form of run IDs.