Currently, a field is flagged as "misconfigured" whenever its jq expression returns null during integration resyncs, and it's logged as a [Transformation Layer] Mapping error at error level in the event log.

Often times though, jq expressions intentionally return null, and it's a documented pattern for optional fields (using // null). The sync does still proceed with that field empty on the ingested entity.

Lowering the log level to debug for null/missing field results would eliminate false-positive noise for customers in the event log. Minimally, the log should make clear that null results may be intentional, surface the affected fields and row counts, and prompt users to verify their mapping only if population was expected.