Allocate checks on both sides
The fictional flow sends customer ID C-17 from an intake system through a connector to a records system. The customer-data owner supplies rules, connector maintainer checks attempts, and target administrator checks saved records.
| Boundary condition | Source owner checks | Connector owner checks | Target owner and coordinator |
|---|---|---|---|
| C-17 missing required status | Correct source status after approval | Record rejection reference | No unintended record; data owner coordinates |
| Attempt sent, no reply | Retain C-17 identity | Mark uncertain attempt and reference | Search C-17 before another write; connector owner coordinates |
| Target rejects field value | Verify intended business value | Retain target rejection | Confirm accepted rule; data owner decides correction |
Forwarding a message does not close ownership
The connector maintainer forwards a lost-response ticket to the target administrator. Who must ensure the customer receives the combined finding?
Show the worked answer
The fixture names the connector owner as coordinator for uncertain attempts. They combine target evidence with the attempt record and report whether C-17 exists; forwarding alone is insufficient.
This allocates responsibilities without claiming any named connector supports status queries or retries. Verify the real systems before agreeing a recovery path.