Bot Occasionally Fails to Update Embeds

[ihasTaco]

In some instances, the ServerQuery bot fails to update embeds as expected. This problem is likely associated with recent changes in the error handling logic, where rate limit errors could be misinterpreted as an indication that a message does not exist.

This problem can result in outdated or missing information in the embeds, which can negatively impact the user experience and the bot's reliability.

We need to investigate the root cause of these missed updates and adjust the error handling logic as necessary to ensure that rate limit errors do not inhibit the bot's ability to update embeds.

Steps to Reproduce:

• Start the ServerQuery bot and let it run over a period of time.
• Monitor the bot's activity to check if any embed updates are missed.
  • You can observe this by checking multiple bot embeds and viewing the timestamps. In my observations, I have seen a delay of up to a minute.
  • The severity of this issue can escalate as more servers are added to the bot's database.

Expected Outcome: The bot should consistently update all embeds, ensuring that the most recent and accurate information is always displayed.

Actual Outcome: The bot occasionally misses updating embeds, which can lead to potential information gaps or outdated data. There's a possibility that this could be due to the bot encountering a rate limit when attempting to update the embeds, but misinterpreting the rate limit error as an indication that the message doesn't exist.

Possible Solution: One potential solution could be to increase the number of attempts. This would enhance the chances of a successful update before the bot gives up. Another approach could be to introduce a delay between attempts, such as 1 second. This could potentially help avoid hitting rate limits by spacing out the requests over a longer duration.

While neither of these fixes will address the underlying issue, they can help mitigate its impact while the root cause is being investigated. In the meantime, I am working on developing a logging system that will aid in identifying and understanding these types of issues.

[ihasTaco]

This issue should be fixed with the new develop build