Thank you so much for your feedback! We are excited to share that this feature is coming and is currently planned as a part of our roadmap for this year.

Hi, just reviewing our integration and we are still very keen to see this feature, specifically receiving the ID of the conflicting schedule via API call, as it would allow us to automate handling conflicts.

Hi, just an update to say that we are still very keen to see this feature. Returning at the very least the ID of the conflicting schedule would make investigation and resolution of these situations a lot quicker (and potentially allow us to have the conflict resolution taken care of by our integration rather than manually).

Hi, just an update to say that we are still very keen to see this feature. I currently have to investigate and resolve these situations manually. Having dealt with several this year so far, I felt compelled to update this request. Please return at the very list the ID of the conflicting schedule.

This will make life a lot easier for our technical team.

Hi, just an update to say that we are still very keen to see this feature. It would allow us to more efficiently resolve conflicts manually where required, and to look at automatically resolving them via our integration.

I fully agree. This was a useful feature in ESS.

This information should be included in both the interface, and the ALP API response so that Timetabling/Echo360 integrations can sensibly resolve "schedule conflicts" in certain cases (e.g. after identifying that two schedules updates are failing because they are conflicting with each other due to a straight swap for time and/or venue)