Hey @tremlas,
good point!
I’ll add that to our GitHub repository, and we can have a look!
I’m sure we can figure out how to make the experience a bit smoother (either by adding it to the debug log or showing a warning in the activity log).
I like the idea of a fake HTTP code – this would allow us to add a little flag in the export table, so you know exactly which file was corrupted!