Read operation-level results
SCIM bulk operations define individual results and allow failOnErrors to stop further processing. A generic batch API can have different rules. The sample ledger is deliberately independent of SCIM wire format; do not infer row success from an outer HTTP status alone.
| Local operation | Target outcome | Result reference | Disposition |
|---|---|---|---|
| B-1 | Created | Target T-81 | Retain mapping; do not recreate |
| B-2 | Rejected: required status missing | Error attached to B-2 | Correct under a new approved payload |
| B-3 | Not executed after batch stop | No target result | Retry as unexecuted work |
Preserve success while resolving the rest
Keep request order only as supporting evidence; use stable operation IDs when responses can be reordered. An absent result is unknown until the contract or status query explains it. Confirm whether dependent rows require a created parent ID before retrying.
A batch of three returns one success, one failure and no result for the third. Can the third be assumed rejected?
Show the worked answer
No. Record unknown or documented unexecuted state, then investigate that identity. Preserve the successful mapping and do not replay its create operation.