0

We are using FindMeetingTimes to get Office 365 Rooms resources which are available in a given time constraint. When number of rooms in Office 365 are less then it is working fine even if multiple hits are made simultaneously.

But eg- If i have 48 rooms and hitting this api simultaneously i'm getting random results instead of getting 48.

Kapil Kapoor
  • 1
  • 1
    Just to isolate the issue out of your code i would suggest you to replicate the issue with Microsoft Graph Explorer or POSTMAN and see if you can still repro the issue. If yes, please share the related info - so that the community can help. – Dev Jan 18 '21 at 16:58
  • Moving this to answer. Consider upvoting it and accept it as answer. So it can be useful to others in the community as well :) Also if you repro the issue share the related info. So that we can help as well. – Dev Jan 19 '21 at 06:28
  • We tried with Postman making multiple batch calls using Graph Batch to Graph API "FindMeetingTime", but getting random results and the entire batch is failing. Eg- If i created 10 batches with 5 attendees in each request and also tried 10 batches with one attendee only. Still we didn't get all results. Out of 10 batches atleast 4-5 batches were returning no results with a Success status code 200. – Kapil Kapoor Jan 19 '21 at 08:40

1 Answers1

0

Just to isolate the issue out of your code i would suggest you to replicate the issue with Microsoft Graph Explorer or POSTMAN and see if you can still repro the issue. If yes, please share the related info - so that the community can help.

Dev
  • 2,428
  • 2
  • 14
  • 15
  • We tried with Postman making multiple batch calls using Graph Batch to Graph API "FindMeetingTime", but getting random results and the entire batch is failing. Eg- If i created 10 batches with 5 attendees in each request and also tried 10 batches with one attendee only. Still we didn't get all results. Out of 10 batches atleast 4-5 batches were returning no results with a Success status code 200. – Kapil Kapoor Jan 19 '21 at 08:47
  • Interesting... I played using POSTMAN/Graph Explorer with the findmeetingtime API - multiple individual API calls (not the Batch ones) and it returned me the right results. Just see that the issue happens only with batch calls or with individual calls also from your end? This may help you to isolate the issue. – Dev Jan 19 '21 at 09:12
  • 1 Failure and Success Response: Status Code: 200 b'{"@odata.context":"...","emptySuggestionsReason":"Unknown","meetingTimeSuggestions":[]}' No of Rooms: 0 Status Code: 200 b'{"@odata.context":"...","emptySuggestionsReason":"","meetingTimeSuggestions":[{"confidence":100.0,"organizerAvailability":"free","attendeeAvailability":[{"availability":"free","attendee":{"emailAddress":{"address":"TestRoom2@xyz.com"}}},"meetingTimeSlot":{"start":{"dateTime":"2021-01-28T07:30:00.0000000","timeZone":"UTC"},"end":{"dateTime":"2021-01-28T08:00:00.0000000","timeZone":"UTC"}}}]}' No of Rooms: 1 – Kapil Kapoor Jan 20 '21 at 07:48
  • Hmm, above i see that it returns "emptysuggestionsreason" - If findMeetingTimes cannot return any meeting suggestions, the response would indicate a reason in the emptySuggestionsReason property. Based on this value, you can better adjust the parameters and call findMeetingTimes again. In scenarios like test environments where the input parameters and calendar data remain static, expect that the suggested results may differ over time. – Dev Jan 20 '21 at 09:15