What the best method to create a backup of bad input data?

A REJECT function routes records that fail validation but does not create a backup file of the raw bad input data.

Mapping errors to an output card records error messages, not a backup copy of the original bad input data.

Enabling backup OnError in the global map settings applies broadly and lacks the specificity needed to isolate which card received bad data.

Enabling backup OnError at the individual card level allows precise control over which cards create backup files when errors occur. This granular approach ensures that only the relevant erroneous data is saved, making it easier to isolate and diagnose specific input problems. A global setting would capture all card data indiscriminately, while per-card configuration targets exactly where failures happen.