Feedback for FlowStudio from I@i****

[johnnliu]

what is your favourite feature?

what is the nature of your bug emergency?

what would you like to see?

Hi there -

1. Is there the potential of improving your runs search feature by actually making a requested date filter a direct call to Azure to retrieve the actual range of flow runs, rather than just filtering after you grab everything. Searching for runs (for instance for a flow that runs a few thousand times a day, and you want to look at just the flows that ran in an hour slot 20 days ago) is onerous because you have to retrieve all the runs right back to 20 days ago to get a result.

Using the Azure PowerAutomate API I can get all runs between a date range, so an improvement in usability of Flow Studio would be to do the same or similar?

2. Also, how do I use the text filter by Trigger or Trigger ID? None of the obvious filters like contains Text return anything. Am I missing something here? Anyway lots of potential over the MS UI, but not as straightforward as it should be

ask FlowNinja anything?

[johnnliu]

thank you for your feedback.

we'll look into filtering run search by date in the API and see if it can work for Power Automate as well. What tools do you currently use to view "Azure PowerAutomate API" do you mean Logic Apps? is this through a service, UX, script or powershell?

Trigger ID or Trigger text is basically automatically mapping to TriggerOutput/body/ID or TriggerOutput/body/Title or TriggerOutput/body/Subject. When the trigger type is more complex, it defaults back to triggeroutput.
Contains should work on trigger output.