You’re offline. This is a read only version of the page.
3
Hi
Recently I created a flow for ouy support team. When a new ticket arrives in our SQL Database, the flow runs.
In the flow, if the ticket has a certain category and subcategory then it sends the person who raised the ticket an email. (in this case, the user has forgotten their ID for a system. We are automating a response that sends them their ID).
The Flow's logic is essentially: If the Subcategory = Forgotten ID, then engage the power automate flow that sends the message.
If the Subcategory is *not* Forgotten ID, then I want it to stop. When I built this, I thought this was as simple as adding a Terminate step to the No branch. This does work as such, but the problem is that Powerautomate is marking the flow as "failing", and is automatically suspending the flow due to too many failures. This type of ticket is rare, and we obviously handle several tickets a day, so the flow is "failing" multiple times a day, every day.
My question is this: is there a better way to "Terminate" the flow on the No step that doesn't mark the flow as having failed to run. It has run, but the conditions for it to do something haven't been met.
Cheers in advance
I hadn't thought to check that! I've made the change, will now let a few tickets come in to test but fully expect you're right. Thanks for the speedy response, couldn't really find any similar questions online.
#1
WarrenBelz
146,587
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,928
Most Valuable Professional
Share
Report
All responses (
Answers (
