Problem with MATLAB Grader report generator: It failed to report students' solution with a 100 grade when using "Best solution as of the due date"

I am using MATLAB Grader to host my course at this time, however, I experienced some difficulties with the report generator of the MATLAB Grader.

When I use the "Best solution as of the due date" in the report generator, the report generated has several problems.

1. Some of the "Best Solutions" (100%, passed all tests) are missed from the report. Instead, other "Best Solutions" (< 100%, failed some tests) defined by MATLAB grader was reported. There were several times the 0 size solution with 0% ones (have syntax errors and therefore failed all the tests) were reported as the best solutions. Actually, students submitted better solutions in term of grade later (before the due time). But the report failed to report those solutions.
2. Some of the students's solutions are totally missed from the report, yes, the students submitted the solutions before the due time. But they submitted it very close to the due time. For example, I set the due time at 11:30pm EST on 1/29/2021, the student submitted the solution at 11:08pm EST on 1/29/2021, the report generated did not include this student's solution. Is there a time zone problem with the report generator?
3. What is the definition of "Best Solution"? size of the file? best grade? I would like best grade first.

Does anyone have similar problems? I have to ask students to verify their grades to make sure the grade reflect what they did for each assignment at this time after I posted their grades based on the report.

Answer 1

[Cris LaPierre]

Please contact customer support.

[Hongjun Su]

Will do.Thanks

Answer 2

[Osmar Tormena Júnior]

I'm haveing similar issues. I've downloaded 3 separate reports (as XLSX files) from the same assignment, due 12 days ago. Every one of them is distinct from the other. Some of them are missing "a lot" of enrolled students that submitted their response within the available time frame.

Is this a known issue? Are there any solutions from support?

[Cris LaPierre]

This sounds like a bug. Please report it to customer support.