Application Consumer key/secret suddenly gets "Could Not Authenticate"


#1

I have had branding set up on my Mokumax account for months and have had no issues posting Tweets.

Over the last 24 hours some scheduled Tweets would post and others would not. If I try to post an immediate Tweet I get “Could not Authenticate.”

I stepped through the code (which hasn’t been changed in months) and it is posting the same consumer key/secret as on my application in dev.twitter.com (MokumaxCraig).

If I delete my consumer key/secret (for MokumaxCraig) and just use the Mokumax key/secret it works consistently.

I’m confused as to what has changed with my MokumaxCraig application. I haven’t changed anything.

Any reasons for the intermittent interruption of service? Could it be a caching issue with Chrome?

Thanks,
Craig