Anthony,
The fix for this issue was checked in to the 13.2 release branch with r28949. We'll make sure to post a build somewhere that you can grab it shortly.

Regarding your question, LabKey has now changed things so that the dataset name is considered the query name for a dataset, when you look in the schema browser for example. Our recommendation would be to use the dataset name for the queryName parameter of those API calls going forward. We should however be backwards compatible in resolving the query name from the dataset label as well with this fix.

-Cory