The busy-slot cache refreshes every 30 seconds. In the best case Senly sees a new Google event within 30 seconds; in the worst case after 1 minute.
In practice: a client who tries to book at exactly the wrong moment could in theory still grab the slot. For very busy calendars: block a buffer margin via your Google Calendar itself.