Since we changed from 2.0-SNAP 5825(I think) to 2.0 release we are seeing a strange behaviour where an appointment in a schedule can be deleted but it wont dissappear from the schedule (however highlighting it will not give you the typical appointment context).  It appears that the appointment is cached.  IF you try and book another app in that slot you will get the conflict warning.  Now if I then restart Tomcat7 it resolves...

I checked the logs and we have no exception relating to schedules

I do have another exception Ill post but I think it probably just needs to be suppressed and associated with an error report.