Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Automate - Building Flows
Suggested answer

Problems with a Workflow for Recruitment with simple approval

(1) ShareShare
ReportReport
Posted on by
Hi,

I am new at power automate and would like to have som help with a workflow for recruiting which bugs me a bit.
Probably just a simple thing since I am new at this. I've made this workflow based on below

My application
The application is a simple Approval flow for recruitments based on a Microsoft Form, as starter for the Recruiting Manager.
I am using Power Automate to get data from Microsoft Form into a Sharepoint List and would like to use the approval part
in Power Automate to handle this.

I've tried to give the flow steps simple explainations. And everything works just fine till after the approval where i fails.
And the system started to setup "each brackets" for the flow in the bottom.





 
Error message, at end of the "APPROVED" Flow
  • Suggested answer
    NW-06062204-0 Profile Picture
    12 on at
    Problems with a Workflow for Recruitment with simple approval
    A lot of times why to get the 0 to 0 column error is because you need the "get item" action. It can't find the item more in detail. Sometimes you need to configure the condition a little different and play around with it. I've even done condition within conditions depending on what I need done. Depends on the logic and what you exactly want done. Use Chatgpt and it can give some pretty good ideas with exact steps to help fix. 
  • David_MA Profile Picture
    11,387 Super User 2025 Season 1 on at
    Problems with a Workflow for Recruitment with simple approval
    Showing your flow is great, but you also need to share the configuration of the action that is causing the error. The only thing I can tell you is that there is a problem with field_6 in the e-mail you are trying to send. 
     
    Some people may disagree, but I would recommend that you leave the original name of the actions and append your description after the original name. While you've done a good job with the descriptions, leaving the original action name allows us to see the exact action you used without having to guess which one it is. Without the action name, all of the SharePoint actions look mostly the same. It will also make it easier for you to know what action it is if you need to edit the flow in six months.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Michael Gernaey – Community Spotlight

We are honored to recognize Michael Gernaey as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard >