I opted to write a work-around by calling a RestClient (or net/http) post to an internal route (so that it goes to web proc and not worker proc), and this action will call the ActionCable broadcast. It's a known issue that's been around for so long, but I don't think there's actual "real solution". Might be wrong, but would be happy if anyone can provide a different solution.