Updated: 2018-01-30 APIs
presence_changeevents are not dispatched without presence subscriptions established with
presence_sub. Relatedly, current user presence status is no longer communicated in
rtm.start. Learn more.
Beginning November 15, 2017, the RTM API's
presence_sub event will be available via presence subscription only.
Dispatching presence events for all users in a workspace is an expensive operation for Slack. A flood of presence events from large workspaces can also disrupt your app's ability to process more useful, timely messages.
By subscribing only to the presence events your app needs to provide presence-dependent functionality, you can reduce unnecessary websocket traffic.
To continue receiving
presence_change events you must:
presence_subevents to the websocket, noting which user IDs your app wants to track presence status for.
usersarray attached to batched
presence_changeevents, dispatched when presence changes for users your app is subscribed to.
rtm.start will no longer include user
online field information in its initial preamble JSON. You'll need to use
users.getPresence to determine initial presence status instead.
Presence events are not currently issued as part of the Events API, therefore nothing is changing on the Events API.
Your app will stop receiving
presence_change events on any websockets your app is connected to beginning November 15, 2017. If your app uses those presence events to direct functionality, your app might not do what it's supposed to do without that information.
Your app will no longer receive the current state of
online information for workspace users when connecting via
Presence subscriptions will become mandatory on November 15, 2017.
Please contact us if you have any concerns at firstname.lastname@example.org.Review other recent updates