# Fix or delete completely broken upload and resulting sequence

**URL:** <https://forum.mapillary.com/t/fix-or-delete-completely-broken-upload-and-resulting-sequence/2781>\
**Category:** Contributing and equipment\
**Created:** [April 8, 2019, 7:11pm UTC](https://forum.mapillary.com/t/fix-or-delete-completely-broken-upload-and-resulting-sequence/2781 "2019-04-08T19:11:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![XCTrails](https://avatars.discourse-cdn.com/v4/letter/x/c0e974/32.png) [@XCTrails](https://forum.mapillary.com/u/XCTrails)\
**Post date:** [April 8, 2019, 7:11pm UTC](https://forum.mapillary.com/t/fix-or-delete-completely-broken-upload-and-resulting-sequence/2781/1 "2019-04-08T19:11:11Z")

</div>

About a week ago, I uploaded a batch of ~700 images/1sec split/no compass angle with the desktop uploader, no issues during upload. Result is a very strange sequencing with some of the images sequenced correctly while many many others ended up as single image sequences along the way. The original images were all geotagged properly and distributed evenly along the road in question.

Reported this in another [thread](http://mapillary.trydiscourse.com/t/why-splitted-in-short-sequences/2765), no response there and not auto-magic fix either.

I’d really like to continue to contribute, but without assistance on why this might have gone wrong and/or if my workflow could have caused this, that doesn’t make much sense for me. Also, a trial&error retry doesn’t look appealing, because I see no way to easily delete all those “1 image per sequence sets” without getting a repetitive strain injury from having to click a couple hundred times…

So any help is appreciated!

---

<div class="post-metadata">

**Author:** ![Gness](https://avatars.discourse-cdn.com/v4/letter/g/3be4f8/32.png) [@Gness](https://forum.mapillary.com/u/Gness)\
**Post date:** [April 9, 2019, 12:28pm UTC](https://forum.mapillary.com/t/fix-or-delete-completely-broken-upload-and-resulting-sequence/2781/2 "2019-04-09T12:28:29Z")

</div>

I’ve had this happen too. I guessed it’s to do with how the images are processed on the servers, rather than how you’re uploading them.  
Pinging an email to [support@mapillary.com](mailto:support@mapillary.com) may be worth while. They have scripts that they can (re)run where things haven’t quite processed right.
