Nope...this is a programming error or server crash/malfunction. I would hazard a guess that the excursion system is housed on a database server which is separate from the bookings database. Somebody has thrown a monkey-wrench into the pot and the calling routine is not getting anything in return. It looks like maybe they have suppressed all error messages, too.