Scheduling Error Alert Improvements
A
Ashley Yip
Currently when faced with a Scheduling ERROR, users receive the message: "Schedule timing clash with another Schedule"
It would be hugely beneficial if more information (i.e. a list of external-id values) were provided alongside the error alert so that troubleshooting attempts can be more targetted and effective.
S
Shane Hjorth
This is a major issue when attempting to integrate Echo 360 recording schedules from a third-party system (e.g. TimeEdit https://www.timeedit.com/)
If there is a timetable clash the API endpoint:
https://echo360.net.au/public/api/v2/schedules
Returns:
{"ERROR":"JSONERROR","PARAM":{"OBJ.STARTTIME":[{"MSG":"SCHEDULE TIMING CLASH WITH ANOTHER SCHEDULE","ARGS":[]}],"OBJ.ENDTIME":[{"MSG":"SCHEDULE TIMING CLASH WITH ANOTHER SCHEDULE","ARGS":[]}]}}
G
Gina Scott
I agree, what schedule is clashing, would save me so much time