WER bug?
It's a lower-case “b” bug, not behavior that causes major problems, but one that probably shouldn't've happened under ideal scenarios. At an event, I probably wouldn't worry about when this happens, unless it has a strong possibility of affecting significant prizing. Additionally, WotC tends to say something along the lines of “the correct pairings are what WER pairs”, i.e. TOs shouldn't be going around and modifying what WER (made by WotC, thus what WotC) decides are the pairings.
<explanation>
Swiss pairings in software work by taking players and sorting them in some order, then pairing them up in that sorting order. (most rounds in WotC software start with players in standings order) If players in this initial pairing have already played each other, then the software needs to be able to fix it, both if there are alternatives at the same point total, as well as if there aren't.
The problem with the “aren't” scenario is that this is not a problem easily processed by computers, so it's difficult to ensure that pairings are processed in an efficient manner: proving that there isn't a valid pairing without pairing down means testing every possibility that could. This means that software will tend to bend the rules relatively quickly, so that it can get a valid pairing without waiting forever on the algorithm.
</explanation>
The end result of all this can sometimes mean what you saw at Game Day: the algorithm reached a point that it balanced expediency over proving it couldn't find a valid pairing, and thus made two pair-downs.