Events continue to get delivered to Streaming API client which uses a session id , the session which has been explicitly terminated
Last updated 2022-02-10 ·Reference W-2545182 ·Reported By 1 users
If Streaming API client uses a session ID and that session is terminated explicitly ,
( for example, grabbing the session from the org using userinfo.getsessionID(); etc ) , events continues to get delivered to Streaming API client even after the session has been terminated (For example by logging out of the org from where the session id was taken)
In any org, grab the session id and use that sessionId to login and subscribing to a pushTopic in a Streaming API client. Once logged into the client, logout from the org from where the session id was originated. Events continue to get delivered to the client even after the parent session has been terminated i.e. By logging out.
Reported By (1)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.