Last match not committed

Hi,
For some reason the last match of our meet was marked as unplayed after we scored it, and posted it to the audience display.
We luckily had a record of what the score was supposed to be and I looked through the db file. Our match 23 was present in the qualsCommitHistory and qualsGameSpecificHistory tables, but not in the qualData or qualGameSpecific. using the last two rows from the history table I manually entered the data into the match control page and it seemed to fix it.

Still not sure why it was marked as unplayed even though it had data for the match in some tables.

Some things to note:
We were running FTCScores for our event, and I was using my hotspot for the upload. FTCScores didn't have the match results either, but its been fixed now too.

I uploaded to FIRST without realizing that match data was missing, Submission ID: 645397472969228324. If we could replace that with the one ending in _full in the zip, that'd be great.

[2019_11_16_10_00_18_AM_err.log](https://github.com/FIRST-Tech-Challenge/scorekeeper/files/3857312/2019_11_16_10_00_18_AM_err.log)
[DB files.zip](https://github.com/FIRST-Tech-Challenge/scorekeeper/files/3857296/DB.files.zip)

Start by reviewing the attached 2019_11_16_10_00_18_AM_err.log and DB files.zip, focusing on match 23 and the qualsCommitHistory, qualsGameSpecificHistory, qualData, and qualGameSpecific tables. Trace how the final match is committed and marked played, then compare the stored history with the missing current rows. Done means the cause of the inconsistent state is identified and the issue has a reproducible verification path.

Written by the indexing model from the issue text.