Hi, @miladk
I can see why you would not want to start over ??
We’ve been talking about this internally, and we are going to provide a button in the next release that will clear the data for any non-pulled images. Basically, it will be like the Destroy button, but it will only affect images that have not been completed and returned to your server.
That should be available in a few days. In the meantime, it would be a good idea to figure out what is causing the errors, or it will continue to happen.
We looked at your report and see that you have a few optimization plugins installed. Have you done any other operations on some of your images while they were waiting for optimization? Something has happened to make images change between the time they were requested and the time they were fetched by our system.
We compare md5 values at several steps, and they do not match in several cases. I can provide the names of a few images, if that will help.