Submitted peer evaluation reverts to "In Progress" with all fields wiped

[MetronLee]

Bug: Submitted peer evaluation reverts to "In Progress" with all fields wiped

Summary

A completed and submitted peer evaluation reverted on its own to an "In Progress" state with every field blank, while the record's own "Last updated" timestamp still shows the original submission time — proving the reviewer made no edits after submitting. This is the second time the same data-loss has affected our team (it previously happened to our Milestone 2 submission), so we do not believe it is user error.

Impact

• A submission that was confirmed as "Submitted" was silently lost.
• Because the platform then reported the evaluation as incomplete, our team was flagged for removal from Orbital over a submission we had actually completed on time.
• The reviewer had no way to detect the loss, since the record still displays the original submission timestamp.

Steps to reproduce (observed sequence)

1. Complete the KedaiFlow peer evaluation and click Submit.
2. Status changes to "Submitted" immediately (confirmed on screen at the time).
3. At some later point, without any further action by the reviewer, the same evaluation shows status "In Progress" and all answer fields are empty.
4. The "Last updated" field still reads 01/07/2026 19:53 — the original submission time — even though the content is now gone.

Expected behaviour

A submission that reaches the "Submitted" state should be immutable and persisted. It should never silently revert to "In Progress", and it should never lose its stored answers. If the record truly changed, the "Last updated" timestamp should reflect that change.

Actual behaviour

• Status reverted from "Submitted" → "In Progress" with no user action.
• All previously saved answers are blank.
• "Last updated" timestamp is unchanged (01/07/2026 19:53), which is inconsistent with the fields having been cleared.

Key evidence

— status showing "In Progress".

— the evaluation with all fields blank / progress lost.

— "Last updated" = 01/07/2026 19:53, matching the original submission and confirming no edits were made afterwards.

The timestamp inconsistency is the smoking gun

The fields are empty, yet the record claims it was last modified at the exact moment of the original submission. Either:

• the stored answers were dropped by a process that did not update the timestamp, or
• a stale/empty version of the record was written over the submitted one.

Either way, this points to a data-persistence or state-transition bug on the server side, not a reviewer action.

Additional context

• This is a recurring issue for our team — the same silent loss occurred with our Milestone 2 submission as well.
• Because a lost submission can trigger removal from Orbital, the severity here is high: it puts teams at risk of being penalised for work they actually completed and submitted on time.

Suggestions

• Treat a "Submitted" record as immutable server-side; block and log any transition back to "In Progress".
• Add server-side audit logging of every state transition and write to a submission (who/what/when), so lost submissions can be diagnosed and recovered.
• Surface the submission history to the reviewer so a silent revert is at least visible.
• Consider a confirmation artefact on submit (e.g. an email receipt) so reviewers have independent proof of a completed submission.

Environment

• Submission timestamp: 01/07/2026 19:53 (SGT)
• Discovered incomplete: on/around 06/07/2026
• Browser / OS: Safari Version 26.5 (21624.2.5.11.4)
• Team: PRTS
• Affected item: peer evaluation for team KedaiFlow, Milestone 2