Activites messages going away after updating to 13.8.0
See original GitHub issueWhich package is this bug report for?
discord.js
Issue description
Since updating to 13.8.0 from 13.7.0 the activity messages on the bots have been going away after a seemingly random amount of time (sometimes 10min sometimes a few hours).
I haven’t changed any code to do with updating the activity messages in like a year and always functioned correctly before. Not getting any error messages either.
In my bots the activity message is updated whenever the bot joins or leaves a guild. And doing so will bring the message back, but after some time it will go away again.
Cannot seem to locate any issues on my end so I suspect it is on discord.js side.
Code sample
'use strict';
module.exports = {
name: 'guildCreate',
once: false,
execute(guild) {
guild.client.user.setActivity(`${guild.client.guilds.cache.size} Servers`, { type: 'WATCHING' });
},
};
Package version
13.8.0
Node.js version
v18.0.0
Operating system
Debian 4.19.132-1 (2020-07-24)
Priority this issue should have
Low (slightly annoying)
Which partials do you have configured?
No Partials
Which gateway intents are you subscribing to?
Guilds, DirectMessages
I have tested this issue on a development release
No response
Issue Analytics
- State:
- Created a year ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Pipelines broken since update to 13.8 | NoMethodError ...
Summary Since upgrading to 13.8, Pipelines are broken as there seems to be some error related to the keep_latest_artifact setting.
Read more >NX Daemon server erroring out after moving to 13.7.1 #8796
I upgraded our workspace to latest NX version (13.7.1). However, I am getting following error with NX Daemon server. > NX Nx Daemon...
Read more >User Guide for AsyncOS 13.8.0 for Cisco Content Security ...
If message filters, content filters, and DLP message actions could not be automatically updated with the names of centralized quarantines, ...
Read more >node.js - React Application not working after a fresh install
lastError: The message port closed before a response was received." I was able to make this message go away by removing the Norton...
Read more >Gen 13 Release Notes (Includes Builds 13.0 and above)
Addressed some issues that could occur when installing or updating ... an issue when attempting to Go To Attachment from an HL7 message's...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Persistence frames of presences are on Discord, randomly resetting is not new, and your update to 13.8.0 is very likely a coincidence in the timeline. Use a sensible interval timer and send the presence again (I would personally advise to keep it above or at least in the region of 1m)
Fair enough and you are correct, it could very well be discord, or even the cloud host if a spotty connection could effect it. It is barely even a nuisance for me in any case. I also don’t know what was or wasn’t changed during the update, I just put this up because it doesn’t seem to be coming from my end and since there was no issue with the system before, I figure it worth mentioning.
It shouldn’t really matter, a single timer going off even every minute shouldn’t effect performance much. I will probably set one about every hour or two just because I don’t care if it is down for that long.