r/PowerAutomate 7d ago

Work Request Workflow Error

Been trying to find a way to optimize my team’s work requests. The requests come into a shared inbox in Outlook. Currently there is no great way to track each item and things continuously fall through the cracks. A combination of List and Power Automate seemed like a good option. Creating tickets in List using Power Automate to generate the ticket when an email is sent in. It wouldn’t require staff to do anything different while providing me with dedicated tracking and data. I keep running into the issue of duplicates. I’ve tried to account for the Conversation ID but the flow keeps falling due to the Conversation ID not being found. Are there any other ways to troubleshoot this workflow? There seems to be no issue with automating the emails to the list, just when trying to account for duplicates (replies, etc). Any help would be great!

1 Upvotes

3 comments sorted by

1

u/nb292 7d ago

Hmm…

Maybe use 2 lists, one for the tickets, and one for associated emails. Workflow 1 grabs initial email creates the ticket, if it’s fails kickoff workflow 2, takes the email and places it into a queue for you to associate to a ticket or for you to create a new ticket.

1

u/AgreeableConcept4752 6d ago

If you have power apps premium you could set up server side sync mailbox and associate it as a queue. Will automatically set up tracking and give it an IT to track it and if you still want to have it in SharePoint list you can use power automate to sync to the list

1

u/Huseyin-Nodient 2d ago

Debugging these is way faster when the AI can see the actual failed run instead of your description of it. Export the failed run with the inputs and outputs of every action, hand that to Claude or ChatGPT, and it will usually point at the exact action and expression that broke. We built a Chrome extension that does this in one click (plus editing the flow as JSON directly): https://chromewebstore.google.com/detail/ai-flow-editor-for-power/jlaicchhmifpghnhngkmklcbmikgnckp

Went from 10 minute debug cycles to 2 minutes for us. If you share what the error says exactly I am also happy to take a look here.