U+0000 (NUL) is valid in Unicode, but unfortunately it's not supported by Postgres (Postgres documentation).
Sometimes the input text has U+0000 (usually test cases to intentionally contain control characters, example), and the flow will fail when writing into Postgres.

Our plan:

• For Postgres target, sanitize and strip U+0000, document the behavior clearly.
• For data written into our internal storage (tracking table), specifically the cached intermediate data, escape U+0000 before writing it down, and unescape it at read time.

❤️ Contributors, please refer to 📙Contributing Guide.
Unless the PR can be sent immediately (e.g. just a few lines of code), we recommend you to leave a comment on the issue like I'm working on it or Can I work on this issue? to avoid duplicating work. Our Discord server is always open and friendly.