As of today, getting 500 errors in ODX/Ingest data transfers using the REST connector does not trigger an error, only warning. This makes it almost impossible to catch. Even if 500 means that something is wrong in the source, we must be able to catch it either to accommodate the possible source limitation (eg. downtime during certain times) or to contact the source admins. For the user, this error is just as urgent as any other.
I propose to make all errors trigger an ODX error (so that the execution package fails), or at least to add an option to set this behavior.
