FindMeetingTimes returns 'LocationsUnavailable' when locations are available

Help Studio
, ,
1

We had a succesfully running automation with the Microsoft 365 package where we look for an available timeslot with FindMeetingTimes and schedule a meeting with Create Event. However since this month when we run the automation we suddenly get an Empty Suggestion Reason ‘LocationsUnavailable’ even though (some of) the locations we’ve added to the array of Locations are in fact available. We haven’t changed anything in our process, so that can’t be the issue. We tried updating the activity package (Microsoft 365) to the latest version (v3.0.11), but unfortunatly with no result.

From several tests we did it looks like it’s caused by the Meeting Duration being > 1 hour (90 minutes). With a Meeting Duration of 30 mins or 60 mins we don’t seem to get this error. But as mentioned, this was never a problem before.

Do more people face this issue? And is it a bug form Microsoft or something we can fix ourselves? We’re eager to hear if anyone has a solution for this.

2

Hi @anka.aktas

I think, The issue may be caused by a change in the Microsoft Graph API or a limitation introduced with longer meeting durations. Try testing with shorter meeting durations (30 or 60 minutes) and verify that resources are available. Also, ensure the Microsoft 365 package in UiPath is correctly configured. If the issue persists, try downgrading to a previous version of the package.

Happy Automation!

3

Thanks for your reply. Like mentioned we already tested with the shorter meeting durations, and because of those not throwing an error we came to the conclusion its caused by the duration time. Still doesn’t anser our question though, since it worked fine before. Microsoft 365 package is configured correctly and downgrading package doesn’t resolve the issue either. Unfortunatly we have no saying in the meeting durations, so simply changing the duration from 90 to 60 minutes is not an option for us.