A few times ago, the conditions, loops, switches, ... were move inside the list of actions. I don't understand the underlying reasons leading to this choice. These actions aren't just some random actions, they're the pillars that structure the flows that we build and we use them every minute. Having to search for them among the list of hundreds of other actions is such a terrible loss of time I'm considering abandoning using Flow... Please move the structural actions (conditions, loops, switches, ...) back to the '+' menu as it was before.
... View more

I know that in advanced mode it is possible to create conditions that have ORs in them, it would be really helpful to have this surfaced in the UI, as a long set of conditional ORs becomes unwiedly to edit. My example above I mention the OR operator, but it would be ideal to have this extend to at least AND, maybe even NOT too?
... View more

It would be a great feature to have the ability to search the contents of a .txt attachment for a string and perform an action based on specified values within the attachment. For example, a .txt document is emailed to a distribution list every hour with results of a data load. The word 'ERROR' is present if the data load fails. However, because the word 'ERROR' is within the body of the attachment, it cannot be filtered using current Outlook Rules. My request is that Flow be able to move this email to a specified folder in Outlook when the word 'ERROR' is present in the .txt document.
... View more