max seeks exceeded
Sort:
I started a few games and it said max seeks exceeded as normal but no games started after several hours and still says max exceeded ??!
Feb 7, 2018
0
#2
You can only have a certain number of unaccepted Daily seeks out at a time. Basically, if no one is getting automatically matched with you, and no one is accepting your seeks, then the site won't let you create more.
Yeah I realise that but they’ve been there over 24 hours now. And in the past they always get taken in a few minutes
Feb 7, 2018
0
#4
Can't say why they aren't being taken. Do you have really restricted ratings?
Same problem. Same setup as always , but won’t start any new games.
No it’s wide ratings 1000 to 1600
I have a similar problem, though I’ve not been told that I have too many seeks. If I create a challenge, it just sits there for days, unaccepted. If I look for open challenges, none are listed. I’m not using exotic criteria, either—just daily, rated, time limit 1 day or three.
Feb 8, 2018
0
#8
You might bug report it, just in case. I'm not in your range so won't see them.
I have the same problem now for a couple of days, cant start a new game. Does anyone know how to cancel previous challenges?
Feb 9, 2018
0
#10
Im having the same problem I only have one daily game and it wont let me create anymore. It keeps saying max seeks exceeded, for over 48 hours and none in open challenges. Also, my criteria is very standard. 300+ and 300-. 5 days, whats the deal here?
Same issue, cancelled current searches using the website, icon of the hand on pawn. Added some games from website and worked fine but tried adding more from the iPhone app and it happened again. Might of worked for one game using the app can’t recall.
Me too!
Feb 9, 2018
0
#13
Sergiovdlm wrote:
I have the same problem now for a couple of days, cant start a new game. Does anyone know how to cancel previous challenges?
You can do it on the website. Is everyone having the issue on the app?
Feb 9, 2018
0
#14
https://www.chess.com/forum/view/help-support/challenges-not-working-1
Should be fixed. See post 17 in the linked topic.