Thanks for the update. This means that Aggregate has returned a response to Enketo that the submission was successful with a 201 or 202 HTTP status (under no other circumstance will a record be removed from the browser queue). So now we somehow have to figure out if the issue is with
enketo.org (enketo-legacy) or ODK Aggregate...
Since it seems hard to duplicate, is there any chance for you to check the logs for the POST to /submission for a submission that is incomplete/empty?
P.S. Since this issue has not been reported by other users, and enketo-legacy is almost obsolete (to be replaced by the new enketo-express app, which you can install yourself), I may not be able to invest enough time to investigate this properly.