· 11 min read
One Core, Many Campaigns: Why Forking the Working Flow Per Tenant Always Drifts
When a product runs many campaigns or tenants, copying the working flow per campaign is the default, and the copies drift. A reliability fix lands in whichever copy somebody was looking at when the bug was reported. Eventually the same inbound event is handled differently depending on which campaign produced it, and triage begins with asking which one. This covers one core plus configuration as data, the test for whether a difference is data or a capability, and how to tell you have already forked.