If a web request is handled by a member other than the primary owner of the session, we schedule the expiration of that session on the primary owner. The command responsible for this serialized both the session ID and the meta data of the session. However, given that the primary owner will already have this information cached locally, there is no reason to include it in the payload of the scheduler command.