Power Platform Community Forum Thread Details

Hello Power Automate Community Team,

I am currently building a flow for SweetCrust Bakery that integrates Microsoft Forms, Excel, and Outlook Calendar. The flow saves successfully, but when I test it by submitting a new Form response, it keeps loading indefinitely and does not complete.

Here is the structure of my flow:

Trigger: When a new response is submitted (Microsoft Forms)
Get response details
List rows present in a table (Excel)
Filter array to match item name
Condition 1: Compare Form quantity against Excel stock quantity
- True branch: Get calendar view of events (V3), then Condition 2 to check if Form collection date/time conflicts with Outlook events
  - True: Send email (Order Available)
  - False: Send email (Schedule Full)
- False branch: Send email (Order Unavailable)

The issue: When testing, the flow hangs at runtime and does not finish. I suspect the problem is with the calendar connector or the date/time formatting from the Form response.

Could you please guide me step by step on:

How to correctly format the Form’s collection date/time so Outlook Calendar accepts it.
How to structure the nested condition to compare Form collection date/time against Outlook event Start time.
Any best practices to avoid infinite loops or hanging runs in this type of flow.

Thank you for your help.

Best regards, Asrar

Screenshot 2026-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Building flows

Hi Asrar,

Since the flow saves but keeps loading during the test, I would troubleshoot it step by step instead of testing the full flow at once.

First, check the Run history and see which exact action is still running. That will confirm whether the issue is Excel, Filter array, Calendar, or one of the conditions.

For the Form collection date/time, make sure you convert it before using it in Outlook actions. You can create two Compose actions:

Collection Start

formatDateTime(outputs('Get_response_details')?['body/CollectionDateTime'], 'yyyy-MM-ddTHH:mm:ss')

Then create an end time, for example 30 minutes later:

Collection End

addMinutes(outputs('Collection_Start'), 30)

Use these values in Get calendar view of events (V3):

Start time: outputs('Collection_Start')

End time: outputs('Collection_End')

For the conflict check, the easier method is:

Use Get calendar view of events (V3) for the requested collection time window.

Add a Condition after it.

Check if the calendar action returned any events.

Condition expression:

length(body('Get_calendar_view_of_events_(V3)')?['value'])

Then compare it to:

Logic:

If length is equal to 0

No conflict → Send Order Available email

Else

Conflict found → Send Schedule Full email

This is usually better than comparing the Form date/time directly against each Outlook event Start time.

Also check these best practices:

Make sure the Excel data is stored in a proper Excel table, not just a worksheet range.

Filter the Excel rows first and confirm only one matching item is returned.

Use Compose actions to display the Form date, converted date, stock quantity, and filtered item result.

Convert quantity values to numbers before comparing them.

Avoid using “Apply to each” unless needed, especially around calendar events.

Add a timeout or scope if the calendar connector is taking too long.

Test each section separately: Forms → Excel lookup first, then stock condition, then calendar check.

In short, use the calendar action to search only the requested collection time window, then check whether it returned any events. If it returned zero events, the slot is available.