power automate error while running the flow: "Cannot read properties of undefined (reading 'properties')"

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

hi expert

i am getting an error when i try t run the flow.

can you help me on this

Categories:

General topics

I have the same question (0)

All responses (10)

Answers (0)

Sort by

Shuvam-rpa 897 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Anonymous as i check in other threads , people solve this issue by just recreating there connection again. so just try to make a fresh connection on sharepoint and outlook action.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
ScottShearer 25,290 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

@Anonymous

It is possible that this is a temporary error - tray again...

If you still see the error, can you expand the trigger and the get items action and post another screen shot?

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

hi I did try multiple times but since yesterday am having an issue and was supposed to send a monthly reminder (first working day of the month) to update the sharepoint list visa lined power apps.

Was this reply helpful? Yes No
nich3play3r 253 on at

Like (0)

Report
Copy link

Link copied!

I'm having what appears to be (?) a related issue, @ScottShearer . I have a trigger set to run every 1 month, then in the trigger Settings, I've added this condition:

@and(equals(utcNow('DD'),'01'), equals(utcNow('MM'),'08'))

When I test the flow without this condition, it runs fine. When the trigger condition is there, the flow fails with the ambiguous "Cannot read properties of undefined (reading 'properties')" error.

Was this reply helpful? Yes No
ScottShearer 25,290 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

@nich3play3r

If you change 'DD' to 'dd' I believe your issue will be resolved.

Was this reply helpful? Yes No
nich3play3r 253 on at

Like (0)

Report
Copy link

Link copied!

Thanks very much for this reply, @ScottShearer . It's weird. Changing the code as you suggest appears to have validated OK, and when I go to test the flow, it says the flow completed successfully. But when I hit "Done," I get the same error, and the execution that supposedly ran successfully doesn't show up in my run history. I've confirmed that the trigger condition is what's causing the trouble by removing it and testing the flow, which succeeds and appears in the run history. Beats me....

Was this reply helpful? Yes No
ScottShearer 25,290 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

@nich3play3r

That is odd....

I ran a test and did not have the same experience - it ran fine and executed as it should have.

You might try using two expressions (hit the + sign) instead of one. Remove the "and" expression and use two expressions on two lines and see if it works.

Was this reply helpful? Yes No
nich3play3r 253 on at

Like (2)

Report
Copy link

Link copied!

Well, this is a hoot, @ScottShearer . Apparently that message is how the flow fails when the conditions in the trigger aren't met? I changed my settings to those pictured below, and the flow ran successfully. I wonder how I'll definitively know whether a flow I'm setting up will actually run on the day and month specified in my trigger conditions....

Was this reply helpful? Yes No
ScottShearer 25,290 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

@nich3play3r

The idea that the "error" is generated when the conditions aren't met makes sense. I should have thought of that....

This is why I love the Power Automate Community site! I am still learning every day.

Was this reply helpful? Yes No
nich3play3r 253 on at

Like (1)

Report
Copy link

Link copied!

Thanks a lot for taking the time to walk through this with me, @ScottShearer . Every time I use the conditions interface I end up wishing it were more robust (code suggestions, at least?) I also wish the "failure" message were more elegant. Since there are at least 3 different ways to code a given solution, showing me a red popup with an ambiguous warning doesn't help me and actually hurts, in this case. What about, "Trigger conditions for execution not met?"

Anyway, I thank you again!

Was this reply helpful? Yes No