[Answered ]-Django Channels. How to avoid the exception RuntimeError: Task got Future attached to a different loop?

After a few days of investigating the issue, I have realized the Exception, RuntimeError, in that case, is just a Warning, not Error.
Because the server doesn't break and the Socket is going on further.
And that "Warning" is still in a Bug stage in Channels developers.
It looks not beauty in the server console, but it works properly.
I tried to try-except it, but can’t figure it out – don’t understand what code invokes the Error to try-except it.