Rate limit headers show full quota remaining, so throttling isn’t the issue, yet the /api/v2/users batch endpoint drops a 422 Unprocessable Entity on the fourth iteration. Running a Node script to sync custom attributes, but the validation rejects the payload without flagging a schema breach. The same JSON passes fine in Postman but chokes in the async loop, so does the v2 batch API strip nested objects during merges or can’t I pass a force flag to bypass it?