BatchProspectFailure

Machine-readable reason: validation_error (the id or the prospect's state refused the change), not_found_or_no_access (not a prospect of this project you can reach), conflict (another request changed the prospect at the same time) or internal_error (an unexpected server fault; the request was valid). conflict and internal_error are retryable: send that prospect again in a new request, under a new Idempotency-Key if you used one, since the same key returns this answer. The other two are not: change the request first. Whether earlier fields were already saved is partiallyUpdated, for every code.

Human-readable reason.

True when the prospect failed on a later field of a batch update after earlier fields — a note among them — were already saved on it, whatever the error code. Read the prospect back and resend only the fields it is still missing, leaving out a note that was already logged, or the note is logged twice. False on every other failure, and always false on a batch removal or a batch task, which write a prospect once: nothing was written to that prospect.

The prospect id as sent.