An OOPS is something a developer or sysadmin needs to look at, always.
I don't think thats the case with an arbitrary failing import: it
could be many different things such as a bad url, through to a code
bug.
If you can reliably separate out 'this is a code bug', sure, but
generating oopses for other reasons would be a step back in our
signal-to-noise ratio around OOPSes.
An OOPS is something a developer or sysadmin needs to look at, always.
I don't think thats the case with an arbitrary failing import: it
could be many different things such as a bad url, through to a code
bug.
If you can reliably separate out 'this is a code bug', sure, but
generating oopses for other reasons would be a step back in our
signal-to-noise ratio around OOPSes.