From 013764c9f2ce4fe76e98a40c52dd4f480ff22ea1 Mon Sep 17 00:00:00 2001 From: mike clark Date: Fri, 19 Jun 2026 15:04:13 +0100 Subject: [PATCH] Fix leave event timeout in trigger events table --- src/pages/docs/presence-occupancy/presence.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/docs/presence-occupancy/presence.mdx b/src/pages/docs/presence-occupancy/presence.mdx index 1feec4ad35..1e80d9f1c8 100644 --- a/src/pages/docs/presence-occupancy/presence.mdx +++ b/src/pages/docs/presence-occupancy/presence.mdx @@ -31,7 +31,7 @@ The following presence events are emitted: | Event | Description | |-------|-------------| | Enter | A new member has entered the channel | -| Leave | A member who was present has now left the channel. This may be a result of an explicit request to leave or implicitly when detaching from the channel. Alternatively, if a member's connection is abruptly disconnected and they do not resume their connection within a minute, Ably treats this as a leave event as the client is no longer present | +| Leave | A member who was present has now left the channel. This may be a result of an explicit request to leave or implicitly when detaching from the channel. Alternatively, if a member's connection is abruptly disconnected and they do not resume their connection within 15 seconds, Ably treats this as a leave event as the client is no longer present | | Update | An already present member has updated their [member data](#member-data). Being notified of member data updates can be useful, for example, it can be used to update the status of a user when they are typing a message | | Present | When subscribing to presence events on a channel that already has members present, this event is emitted for every member already present on the channel before the subscribe listener was registered |