ActionCable callbacks order

rubyonrails-core
1

Hi,

Is it possible that ActionCable callbacks are called out of order or in parallel? We are facing a problem that callback for :disconnected is processed before :connected in our heavy utilized server. I would expect that the order of those callbacks and their serialization is guaranted by framework. Is it by simplicity of the design or a bug?

Thx jkprg

2

You could try using just a http call (I recommend setting up an api with jbuilder), or indeed broadcasting back a success message PrepaidCardStatus