If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Wanted to double-post this to make sure everyone sees it:
Originally posted by VPI97
The faulty data has been cleaned up...this type of thing can occur if there's a timing issue in the draft app.
The logic is pretty cut and dry...once someone picks, the app marks that player as the selection, then checks all the lists in the system to see if that player was on any of them. If so, it removes the player, re-sorts the lists, then checks for an auto-pick. If there's an auto-pick, it stays in the loop until someone has their list turned off.
Why this problem occurred is because somewhere in the loop, the code quit running...that could be because of a lost connection back to the database or something as innocent as the person who made the pick closing their browser (or navigating to another page/hitting refresh/hitting stop) before the code was finished. Basically, the code quit running in the middle of one of those loops...that's why that one player wasn't cleared from a couple of lists and why the auto-pick wasn't triggered.
In short, when someone makes a pick, they need to wait until the code is completed (i.e. the draft app refreshes itself in their browser) until doing anything else.