This is most likely due to a prefix mis-match with the file and what CloudHealth is expecting.
Be sure to double-check the file prefix to ensure that it matches what is showing in CloudHealth. Files that don't match up (even ones previously processed where a prefix was updated) will not be processed so it's important to note any prefix changes to avoid this phenomenon.