Unable to test flow on Email Student when a loan is created

[ecoreano]

On Video 6, at the mark of 16:01, when I go click on "test", it gets stuck with the spinning wheel. It doesn't load window. It spins for several minutes and then error out with this message:  "Flow run timed out because the starting action was not performed. Please try again."

BTW, my wife is also doing the learning on her own as well and got stuck in this same spot. She was actually ahead with the learning module and now isn't able to move forward from this spot.

[Oyin]

I ran into the 'spinning wheel' situation a lot of times especially in the power automate module. Try to turn off the New designer or New look button at the top right corner of the page before the test and any other time you encounter this. This was the only way I could move forward. I hope it works for you!

[BCBuizer]

Hi @ecoreano ,

After clicking the test button, you still need to perform an action to trigger the flow run, in this case the creation of a new row in the Loans table. If this is not done, indeed the flow run will time out.

All of this is shown in the video between 16:10 - 17:10.

[Ekene]

Hello Oyin,

How were you able to solve the email connection problem in the workflow with copilot?

[kashjoyin]

I was able to test the flow successfully with the co-pilot created one. But with the created from blank flow, it just keeps rolling...I have done it from scratch a few times in case i'm doing something wrong but same problem. Anyone else experiencing this?

[BCBuizer]

@Ekene : a suggested fix has been posted in this topic: Re: Unable to add an Email to the workflow - Power Platform Community (microsoft.com)

@kashjoyin : for both flows you mention, an item needs to be created for the test to work. Both flows are automated flows, meaning they are triggered by a change in data. If your flow did not exist and was turned on when such a change happened, when testing, you only have the Manual option available. If you select that option, you will still have to trigger the flow by making a change in the data. This is shown in the videos for both flows, so following the steps in the videos should help you get past any issues.

In case the flow did exist and was turned on whilst a data change took place, the automatic test option becomes available, allowing you to use that past event to test the flow without the need to perform manual actions.

[kashjoyin]

I understand what you mean. The trigger is for the loan table to change which I can achieve by checking out a book. When I do this with the "co-pilot created" flow, the flow runs successfully. But when do the same process with the "created from blank" flow, it doesn't work. It just rolls around till it times out. This means it does not recognize my trigger. I am not sure why because during creation I picked Loans as my table name.

[BCBuizer]

Hi @kashjoyin ,

Can you please verify the parameters set for the trigger of the flow you created from blank? They should look as in the video:

[kashjoyin]

Those parameters were correct.

However, I have solved it.

I compared every single part of the working flow to the failing flow.

I realized that the dataverse connection was slightly different so I picked the exact connection for the working flow and the test was successful. 

However the other two connections were created auto when I created the trigger initially.

Not sure why they didnt work.

Thank you for trying to help @BCBuizer 

[Oyin]

Hi @Ekene ,

Have you been able to resolve the issue?