The Contoso Convergence, Episode 4: Page Seventeen
An Advanced Dungeons & Dynamics 365 session. Episode 4 of 14.
Previously on: Episode 3, The Labyrinth of Financial Dimensions, the party mapped a chart of accounts that turned out to be three different structures stapled together, and found a dimension called TEMP_DO_NOT_USE quietly carrying eleven thousand postings nobody remembered approving.
Every SOW has an appendix nobody reads until they have to. For Contoso, that appendix was page seventeen, the integration list, and it went missing before the party ever set foot in the building. This episode, they finally find it.
The Session
GM: Vex finds page seventeen. It was stapled into the wrong appendix.
Vex: Six integrations. EDI for two vendors, a freight audit feed, a payroll export, a legacy AR aging tool, and… this one.
Thorne: Which one?
Vex: No name. No owner. Just an endpoint.
Ai. Cassiopeia: I have log access. It has been failing silently since three weeks ago. Retry logic swallows the error.
Sable: Failing into what?
Vex: (long pause) It posts landed cost adjustments. Into the shadow ledger.
Marge: So the spreadsheet Priya built wasn’t tracking a gap in the system. The system was quietly feeding it.
Thorne: Then the six figure variance from episode two…
Ai. Cassiopeia: Is not a variance. It is three weeks of unposted freight true ups sitting in a dead queue.
The room goes quiet. Somewhere down the hall, a fax machine that shouldn’t still exist starts printing.
Vex: (staring at the endpoint) This integration doesn’t have a name because whoever built it never expected anyone to find it. Look at the naming convention. It doesn’t match anything else in the environment.
Sable: It’s not part of the original build.
Vex: No. It’s a patch. Somebody built this after the fact, quietly, to route around a problem they didn’t have time to fix properly. And then never told anyone it existed.
Marge: Which means it was never in scope for testing. Never in scope for documentation. Never in scope for anything.
Ai. Cassiopeia: Correct. It has been running in the dark since before this engagement began.
Thorne: (quietly) We didn’t inherit a shadow ledger problem. We inherited a shadow integration that created one.
The workaround nobody admits to building
Every party in this scenario has been telling the truth as they understood it. The CFO didn’t know the integration existed. Priya didn’t know her shadow ledger was being fed by something outside her control. Even the original consultants probably didn’t know, since this integration was never part of the documented build. Somebody, at some point, hit a wall, needed the numbers to move, and built a bridge nobody else was told about.
This is the quiet failure mode that doesn’t show up in a status report. Not a missed deadline. Not a scope change. A small, undocumented patch, built with good intentions under real pressure, that outlives the person who built it and the reason they built it. Nobody decided to create three weeks of silent failure. Somebody just wrote retry logic that swallowed errors instead of surfacing them, because surfacing them would have meant admitting the patch existed in the first place.
The lesson here isn’t “don’t build workarounds.” Sometimes a workaround is the only thing standing between a business and a missed close. The lesson is that a workaround without an owner, without documentation, and without visibility into its own failures isn’t a bridge. It’s a debt that compounds silently until someone like Vex has to go digging for an endpoint with no name.
What happens next
The party now knows exactly where the six figure variance came from, and it isn’t a variance at all, just three weeks of backlog stuck behind a silent failure. But knowing the cause and fixing it in time are two different problems. The CFO wants an answer before his board call, and he’s giving the party one hour to decide whether to patch the integration live or freeze it and clean up the backlog by hand.
Next episode: Episode 5, One Hour (coming soon)
If there’s an integration running quietly in your environment that nobody currently owns, you’re not the only one. Gamifying the Enterprise: Game Mechanics for Continuous Proficiency is available now on Amazon: https://www.amazon.com/dp/B0GY3VWLVX
And if you want the configuration discipline that keeps workarounds like this one from going dark in the first place, start here: adnd365.com/start
A Tinkerers Notebook 