[FIXED] Discord Client & Asyncio multiple Tasks going all crazy after a while

Issue

Ok so, i have a Discord bot, declared like such in a main.py:

 import discord
 import asyncio
 #
 import settingsDB
 import logger
 #
 import module_one
 import module_two
 import module_three
 import module_four
 [...]
 
 client = discord.Client()
 botToken = settingsDB.getBotSetting("DiscordToken")
 
 # on_ready event stuff
 @client.event
 async def on_ready():
      # stuff
      # [...]
 
 # on_message event stuff
 @client.event
 async def on_message(message):
      # stuff
      # [...]

 # Tasks functions
 async def taskOne():
      while True:
           cycle = settingsDB.getBotSetting("taskOne_Cycle")
           # calling for stuff in module_one.py
           # stuff
           # [...]
           await asyncio.sleep(int(cycle))

 async def taskTwo():
      while True:
           cycle = settingsDB.getBotSetting("taskTwo_Cycle")
           # calling for stuff in module_two.py
           # stuff
           # [...]
           await asyncio.sleep(int(cycle))

 async def taskThree():
      while True:
           cycle = settingsDB.getBotSetting("taskThree_Cycle")
           # calling for stuff in module_three.py
           # stuff
           # [...]
           await asyncio.sleep(int(cycle))

 async def taskFour():
      while True:
           cycle = settingsDB.getBotSetting("taskFour_Cycle")
           # calling for stuff in module_four.py
           # stuff
           # [...]
           await asyncio.sleep(int(cycle))


 client.run(botToken)

settingsDB refers to settingsDB.py where all the function querying my DB are stored and can change depending on user inputs updated via another source not related with Discord bot (via website PHP).

logger refers to logger.py where i'm wrting into a txt file stuff that i want as logs.

Under on_ready event i wrote:

 @client.event
 async def on_ready():
      print('Logged in as {0.user}'.format(client))

      try:
           asyncio.ensure_future(taskOne())
           asyncio.ensure_future(taskTwo())
           asyncio.ensure_future(taskThree())
           asyncio.ensure_future(taskFour())
      except BaseException as err:
           logger.logger('Unexpected error > "' + str(err) + '" / "' + str(type(err)) + '"')
           raise
      

I've changed this part multiple times over the previous days because i wanted to have real asynchronous behaviours, but couldn't get it.

But whatever i've wrote here, i've noticed that after a couple of hours, the 4 Tasks, and even the bot itself was being launched randomly and not according to the await asyncio.sleep(int(cycle)) that each task###() has at their end.
Wierdest part is that the bot itself was firing the print line therefore telling me that it logged in again (???)

I have to mention, that taskOne() can vary quiet a lot depending on the stuff it processes, can go from 1 to near 20 minutes long.

Any ideas why it behaves like that ?
Please tell me if you need more details.

---

After @PythonPro recommendations i've changed on_ready function:

 G_hasLaunched = False

      @client.event
      async def on_ready():
           global G_hasLaunched
           print('Logged in as {0.user}'.format(client))
 
           if G_hasLaunched == False:
                G_hasLaunched = True
                try:
                     print("creating tasks")
                     asyncio.ensure_future(taskOne())
                     asyncio.ensure_future(taskTwo())
                     asyncio.ensure_future(taskThree())
                     asyncio.ensure_future(taskFour())
                except BaseException as err:
                     logger.logger('Unexpected error > "' + str(err) + '" / "' + str(type(err)) + '"')
                     raise

Still trying to figure out if it fixed the whole mess

Solution

If a task is blocking (non-async), and it takes too long, the bot's connection to Discord times out and from the user's viewpoint, the bot has gone offline. When control is returned to the bot's connection logic, it reconnects to Discord. Once it has reconnected, it will fire the on_ready event again.

If you need to execute blocking logic, you can refer to this StackOverflow answer. To deal with on_ready firing every time you reconnect, you should have a variable that is set to False at the beginning of the script. Then, in on_ready, check if the variable is False. If it is, set it to True and start the tasks in your modules. The key point here is that the tasks are only started once.

Answered By - PythonPro