"BadRequest" Stuck Sync

[shiftyscales]

Describe the bug?

Following up on the recently documented issues around "Stuck Sync" issues like "Too Many Requests"- I've found there are some other potential causes.

User EvanTheHusky approached me regarding a stuck sync issue (log included below). "Upload failed: BadRequest" and "Couldn't upload assets". It also throws exceptions during this process stating "An attempt was made to transition a task to a final state when it had already completed."

Relevant issues

Similar issues such as #3211 - although this appears to be a different underlying cause.

To Reproduce

Uncertain.

Expected behavior

Syncing should proceed as normal and the records should be uploaded.

Log Files

DESKTOP-4315GTO_-2022.1.28.1310-_2022-09-05_19_37_42.log

Relevant error appears to start at line 898.

Screenshots

No response

How often does it happen?

Sometimes

Does the bug persist after restarting Neos?

Yes

Neos Version Number

2022.1.28.1310

What Platforms does this occur on?

Windows

Link to Reproduction Item/World

No response

Did this work before?

I Don't Know

If it worked before, on which build?

No response

Additional context

The user had a number of things saved they aren't immediately willing to discard by deleting unsynced records.

When @ProbablePrime is available- I'd appreciate if he were to put his eyes on this for a moment to see if he notices anything I didn't, or otherwise if he has any suggestions for how the user could preserve their data while clearing their unsynced records.

Reporters

TheVirtualHusky evan#0081

[ProbablePrime]

Setting assignee to myself, to remind myself to take a look as Shifty has asked.

[ProbablePrime]

Unfortunately the bad request error doesn't give me anything to go on. Its likely that there's something wrong with that asset though.

Depending on what it is, it might be best to use the Neos Bot commands to delete it by id. I'm not sure if that will work because it hasn't been able to sync.

[bontebok]

@ProbablePrime I assisted EvanTheHusky with resolving it with a suggestion from Shifty to swap out the failed asset. I have the asset file from them that caused the issue that we had to swap in order for syncs to continue, I will send this to you on Discord.