Hi @maxim, as the library that I’m using is listening to a websocket, I found this thread (which is a bit old now) that has the same problem : Modelling temporal workflows for websockets and event streaming
Is that still the solution today ? And what do you mean by “separate” ? I would have find it quite useful to encapsulate the websocket into a workflow or an activity to start it again automatically if it goes down, so an out-of-temporal process that send signals to my workflow would require control management (like the one mentioned, or to kill it if the main workflow is stopped).
Sorry to bother you especially with that, but as you were the one answering this topic, you may remember that 