In some cases* it can happen that the server publishes a state update before the client had the chance to subscribe to that state. This issue has been covered in our [community](https://state-less.cloud/community/post-d9be6e72-55a6-4917-83ca-776f61d9410e) and [this StackOverflow post](https://stackoverflow.com/questions/77902367/how-to-solve-this-pub-sub-timing-lifecycle-issue). We have a vague idea how to solve it, but it still needs additional thoughts and discussion before it can be implemented.