I’ve been using TweetDeck for a while now and it’s been rolling along smoothly, but recently when I was scheduling some updates all of a sudden it tells me “scheduler error – no credentials associated with this account”
??Since when?? I haven’t added any new accounts and they’ve all been working just fine up until now.
So when I tested out trying to send scheduled updates to each of my accounts I discovered that Facebook was the culprit. All I had to do was remove my Facebook account from my TweetDeck settings and then re-add it back again.
Voila! Everything is running and scheduling as usual again.
If you’re having this error yourself I’d suggest trying to schedule individually to each of your accounts until you narrow down who the suspect is, then delete and re-add that account to your TweetDeck.
Super easy fix!
Hi! I’ve been searching on and off for a solution to the same problem, but nothing seemed to work. After a few months I suddenly found your post and was happy like a, like, well, like a very happy person. I tried the solution as described above, to find out… it, too, doesn’t fix the problem (at least, in my case). 🙁
So I went off on another (the last!) search frenzy and finally came across the following remark: “Log out of TweetDeck using the triangle with exclamation mark in the upper right corner. Restart TweetDeck, log in and it’s smooth sailing again from here on in.” Which… worked!
Hopefully this’ll help out someone else, too.
Correction: I think your solution actually does help. I just noticed the different status errors. Your error states “Scheduler error – No credentials associated with this account”. Before I removed the Facebook account it said: “Scheduler error” and something about a ‘bad timer’ (?). After removing the Facebook account it started saying “Scheduler error – Bad password”, so your method did something. The solution I describe works for the ‘bad password’ thing.
Hi Rene,
Awesome, thanks for the tip and the clarification – hopefully between the two of us we’ll have the info to help folks get back up and running!
Same issue here. I logged out and logged back in and still had the same problem when trying to schedule a tweet. I tried changing passwords, and that worked! Weird.
Thanks David, good to hear all possible fixes for sure!