I have developed an event reservation form for teachers and staff at my school, to incorporate some location conflict checking. When scheduling an event, the user enters the Start DateTime and End DateTime; at that point, deluge scripting searches the database of events, looks for any overlaps in the times for existing events vs. the requested event, and then updates a dropdown menu of available locations. Thus, if a location is already booked, it is unavailable for future reservations during that time slot.
There's been a bit of a learning curve by my end users with the system, and I've had to administratively delete some submissions which were incorrectly submitted. I am now getting unusual behavior that some locations are unavailable to reserve, even though there are no current records occupying that time slot - BUT some of the locations sound familiar as having been selected in these past erroneous records. For example, I have one location that never comes up as available until September of next year; I seem to recall a teacher submitted an event and accidentally advanced the calendar selection by a year, after which I deleted that record.
Given that Enterprise accounts have a Record Audit feature which shows a history of the records' behaviors, when a record is "deleted", could it be that it is not, in fact, fully deleted, and that Deluge is picking up records that are invisible to us as the end user but still present in the system? If so, is there any way to avoid this behavior?