Website Failed Version Update Handling

M

Moonsong

Creator
There is currently no way to determine why a version update fails to process, nor is there a way to clear the version. This means you have to keep incrementing the version, trying again, and then if it fails, rinse and repeat (since if you retry the update, it complains the version is already uploaded even though you can't access it).

Please add the ability to manage failed versions (and see why they failed).

Thank you.
 
Upvote 0 Downvote
When it fails, it shows you a reason in the little upload notification in the corner. You can go to the edit page for your mod, click the "Versions and variants" tab, then delete versions. You may need to refresh the page. Versions that fail to process are not created, though.
 
Well, here is what happened (twice):

1) I uploaded new version.
2) I received a "failed to process" with no additional details (it failed during the duplicate check).
3) There was nothing on variants/versions.
4) I attempted to re-upload.
5) I was told the exact version already existed. It was not present on the version page.
6) I incremented the version and repeated steps 1-5 (two attempts).
7) 4.3.0 was the version on the main page.

I got busy, came back hours later. Both versions were on the version page (and the latest, 4.3.2 was the public facing version on the mod page).

I hope this can help you figure out what went awry!
 
You'll need to show which mod you're talking about. Just a link is fine.
 
Okay, I'm pretty sure it's this mod in question. The logs confirm what I said: your first upload completed successfully, then you tried to upload the same version again (which failed), then you must have deleted that version and successfully uploaded it again.

Without more details, I can't provide any additional help. It could be that what you thought was the upload failing was a different issue. In your list of steps, 3 is because you needed to refresh the page. If you had, you would have seen the uploaded version (unless it was still processing after the notification stopped). I'm not sure what happened; the logs only show successful 4.3.1, duplicate, then successful 4.3.1 again.

If this happens again, please take a screenshot and try to keep the page open for further debugging. Sorry I can't be of more use!
 
You must log in or register to reply here.
Back
Top