tl;dr The issue has been fixed and all the votes are caught up.

With the recent deployment of vote logs, a new issue has arisen since last night. When authors edit posts, the network broadcasts a comment operation, there is no way to tell the difference between new content and edited content without making another network request to retrieve the entire article. The bot correctly adds it to the vote queue. The queue will eventually get to the post when the time is right and upvote it.

Simplified diagram of the vote queue

Processing the vote queue does a lot more than simply upvoting articles, the issue comes into play when trying to add the article to the user's vote log. The vote log has unique indexes set on certain properties, correctly preventing double logging of articles. After an upvote is made, the article gets added to the vote log. If the article doesn't exist, then great, it would add it and queue up the next article to be voted. Otherwise the database would return the error and would break the vote queue loop. Uh Oh! Normally the queue is self correcting which is why the error only started majorly occurring since last night. However, the fix is quite simple, we catch the error and move on. The fix has been deployed and all the votes stuck in the queue have been processed.

Join the party on Discord

Official Discord server invite - https://discord.gg/hT7gw4B

Come by, say hello, ask questions, and have fun.