It appears that on 12/18/09 the DM Bot resent all previously sent RTs
This is an undesireable situation. We now have duplicate RTs as output of the account, and the content, in a number of cases, is quite outdated. Do you know what caused this, and can you put into place something to prevent it from happening again?
Thanks,
Joan Starr
California Digital Library
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Josh Owens on 24 Dec, 2009 06:04 AM
Joan,
Thanks for contacting us, we are very concerned about the duplicate tweets, we work very hard to avoid such duplicates.
After looking into it, I am still trying to find the root cause, but in the meantime I did find some bugs in our tweet tracking system and I am resolving them tonight (http://twitter.com/tweethopper/status/6991218530) and tomorrow. Keep an eye on the tweethopper twitter feed (http://twitter.com/tweethopper) for updates.
3 Posted by joan.starr on 24 Dec, 2009 06:05 AM
I am out of the office, returning Monday, January 4th, 2010. I will respond to your message when I return. Thank you for your patience.
4 Posted by joan.starr on 24 Dec, 2009 03:57 PM
Hi Josh. I have also reported that the RSS Feed not failed to work at all. You'll see another ticket from me but I forgot to put my email address.
Thank you.
Joan Starr
------Original Message------
From: Josh Owens
To: Joan Starr work
ReplyTo: Tweet hopper Support
Subject: Re: It appears that on 12/18/09 the DM Bot resent all previously sent RTs [Problems]
Sent: Dec 23, 2009 10:04 PM
Support Staff 5 Posted by Josh Owens on 22 Jan, 2010 06:49 PM
Joan,
I've added support for better tracking of direct messages to ensure this doesn't happen again. The root cause was SQL row contention and multiple jobs running at once. I added locking to ensure they only update the twitter account one job at a time, so we track direct messages properly now.
The fix was deployed as of last night.
Josh Owens closed this discussion on 22 Jan, 2010 06:49 PM.