Team Conflict Avoidance System Erratic Behavior

The below video shows me discovering conflicting games that were auto-scheduled by the StackSports scheduling system despite a team conflict rule having been previously created to prevent this. Usually the system adheres to the team conflict rules I create. Sometimes (inexplicably) it doesn't.

This video is an excellent example showing this is actually a bug, and not intended behavior. After making a subtle adjustment to a game time, it's like the existing team conflict rule "woke up", and triggered the red alerts it should have done all along. In fact it should have scheduled these games in a way to avoid the conflicts in the first place, and therefore the alerts wouldn't have ever had need to exist.




This video shows problems such as:

  1. Conflicting games that should never have been scheduled at the same time (based on the team conflict rules that were already defined).
  2. Missing alert/warnings for "error" games that have problems (i.e. the games with times that violate the team conflict avoidance rules).
  3. Team Conflict rules only become active after game time is altered.
  4. Refresh of web browser required for some changes to be visible.
  5. Team Conflict rules only become active after the conflict time is adjusted (need to double-check & verify this).
  6. Visual scheduler false errors about being offline.
  7. Refresh of web browser requiring several steps (clicks & typing) to get back to the filtered game screen to continue working.

These bugs are very time-consuming to deal with. This is just a glimpse into what it's like to work with the StackSports LeagueConnect scheduling system.

Comments

Popular posts from this blog

StarTech PEXM2SAT3422 initial problems

No grace in verbatim communion prayers