firstly - this should only happen on a small number of images in a given project and will not cause the tool to stall (unlike in previous releases where the thread would just die when this happens). if this happens to you, download the image/s manually from the frontend and upload them into your order after the tool's finished.
this exception happens occasionally when the image content endpoint returns a 404 page. our error handling considers a request to be successful if the status != 500; rather, it should consider a request to be successful if the status == 200. trivial fix that I'll include in the next release.
firstly - this should only happen on a small number of images in a given project and will not cause the tool to stall (unlike in previous releases where the thread would just die when this happens). if this happens to you, download the image/s manually from the frontend and upload them into your order after the tool's finished.
this exception happens occasionally when the image content endpoint returns a 404 page. our error handling considers a request to be successful if the status != 500; rather, it should consider a request to be successful if the status == 200. trivial fix that I'll include in the next release.