ActionConditionFailed. The execution of template action 'Start_and_wait_for_approval_from_Controller' failed: an unexpected exception encountered when evaluating branching condition.

[Ronin_Tico]

I apologize for the long thread in advance!!!😂

I have a strange situation with a Power Automate and I am hoping someone might see where I am going wrong with it.  I will do my best to explain, provide some pictures, and can provide more details for any questions.

I have a Sharepoint list that has a variety of fields, but only a couple control the Workflow. Here are the fields and their types:

Status - Single line of text

BU Approver Check  - Yes/No (Toggle)

Finance Approver Check  - Yes/No (Toggle)

Controller Approver Check  - Yes/No (Toggle)

ApproverCnt_Ref - Single line of text

I have a Power App that ensures each field above gets the necessary information for the workflow.

Now here is the flow:

Steps 1 & 2

At Step 3 I have a Switch which checks the "ApproverCnt_Ref" field for a number from 1 to 3.

Based on the number stored in that field, it takes action to Start and wait for an approval. The count in that field is based on the 3 toggles noted above. The Power App does a count of them and stores that number in 2 different fields.  One is actually a Number field which did not play nice with this Switch since they are stored as "Floats" and for some reason the int() function would not work to convert them. So to work around it, I adjusted my Power App to store the number as text in the Single line of text field as well and it seems to work.  Here is where the problem comes in.

See figures 1&2 below as a reference.  It gets past step 2, goes to the switch in step 3 and correctly hits Case 1 in my testing, and then bombs when it tries to work the Approval process.

So here are important points.

1. This is in a new Environment in my Power Platform and Approvals have not been provisioned.  The first run of this flow should provision it.
2. I exported the flow and took it to my Default Environment where Approvals are provisioned and have run just fine in the past, but I still get the same errors.

Now, I also tried running this flow with a 2 approver count and something different happened which was strange as well.  Use the below images as a point of reference as well.  In the first image, you can see the input and I have the three toggles.  So in the second image you will see Case 2 where I have a condition testing specifically for what two toggles are set as "True" at the same time. In screen number 3 you see the test run and it shows "No inputs" for the condition.

[Ronin_Tico]

UPDATE:
I did get the Approvals installed in the new environment by setting up a basic flow that I triggered for a basic approval.  I then tried my flow again with a single approver and still getting the below error.

I feel like it is linked between my cases being numbered and how I had to handle the Approver Count field as a "type", but it seems the conventional stuff that I have tried is not working.  Any ideas are GREATLY appreciated!

[Ronin_Tico · Accepted solution]

I found my answer.  The problem was in the Condition/Switch piece.  They were not properly accepting the direct input from the SharePoint fields.  I had to setup variables for the needed fields.

So for the ApproverCnt_Ref single line of text field, I had to use the int() function to convert it to an Integer.  Then I had to setup 3 separate Binary variables for the toggles.  I changed the flow around for those variables and it is now working.