System fails to process E2B R2/R3 files with UTF-16 encoding
Before:
When a valid E2B R2/R3 file with UTF-16 encoding was uploaded, the system did not recognize the file type. As a result, the file remained unclassified and was not processed further. (38341443)
After:
The system recognizes and processes E2B (R2/R3) files that are encoded using the UTF-16 standard.
Impacted Areas:
E2B Intake across all ingestion routes:
- Manual Upload
- sFTP (Interchange Service)
- REST API
Parent topic: What's fixed