Answer
Double-check whether the field belongs at the top level of the API payload or nested inside a related sub-entity in that task's configuration — placing a top-level field (like a reference number) under a nested entity's structure by mistake is a common, easy-to-miss misconfiguration that produces exactly this symptom.