Who watches an integration after go-live? The question nobody settles at handover

An integration goes live, everyone signs off, the project closes, and the question of who watches it from Monday never quite gets asked. It stays open until the morning it matters, and by then it has stopped being a question and become a reconciliation exercise.

Google shut down the Content API for Shopping last month, a year after announcing it. Some organisations knew that morning. Others found out weeks later, when somebody asked why the ad spend was flat and revenue was not moving with it. Identical upstream event, and the whole gap between those two outcomes came down to whether anybody had been given the job of reading the deprecation notice.

Google is the considerate end of the market. Most platforms give you less, and there is research putting it at roughly seven times out of eight that a breaking change arrives with nothing in the specification to warn you (Yasmin, Tian and Yang, ICSME 2020, across 1,368 public REST APIs). The smaller tools in a stack are worse than that again.

Which is why I think the ownership question belongs in writing rather than in goodwill. I keep a list of thirteen questions I put to any integration before it goes in. Three that tend to end the conversation early:

1. What happens to a record that fails to send? If the answer is anything other than retried, then parked somewhere you can see it, it is being thrown away.
2. If this stops working tonight, what tells us, and how quickly? If the answer involves a person noticing, there is no monitoring.
3. If we wanted to move this to another provider next year, what would that take? This one reveals more about a supplier than the other twelve put together.

Curious what this room does with the first one. Does your vendor paperwork say anything about failed records, or does it only ever come up after the first incident?

Disclosure: I build and maintain these for a living, so I am seeing it from the supplier side.