Version 2025.2. If the data contains characters that are considered as XML invalid (e. g. 0x05), Origam workflow fails to store the data in the context store, because it is using XML internally. There’s no way to prevent invalid characters from appearing in the data. They can come from external sources. This problem already appeared when processing mails from IMAP, where it was addressed by sanitization or putting the message to badmail.
A solution for all possible incidents needs to be implemented and the IMAP solution should be revisited.