Where connections fail.
NO OWNER
An integration nobody maintains until it breaks.
NO MONITORING OF LAST SUCCESS
Silently stopped, discovered weeks later.
ASSUMING DELIVERY
Treating acceptance as arrival.
NO RECONCILIATION
Divergence compounding unnoticed.
RETRYING NON-IDEMPOTENT OPERATIONS
Duplicates created by the retry itself.
TREATING TIMEOUTS AS FAILURES
Repeating work that actually succeeded.
NO TIMEOUT AT ALL
One slow provider exhausting your own resources.
TWO-WAY SYNCHRONISATION WITHOUT CONFLICT RULES
Data flapping between systems.
NO RECORD OF WHAT WAS SENT
Discrepancies impossible to investigate.
MAPPING DECIDED IN CODE, UNDOCUMENTED
Nobody able to answer what happens to a field.
CREDENTIALS SHARED ACROSS ENVIRONMENTS
A test system acting on production data.
TEST MESSAGES REACHING REAL CUSTOMERS
Damage done in seconds.
PROCESSING WEBHOOKS SYNCHRONOUSLY
Timeouts, and the sender retrying endlessly.
NO SIGNATURE VERIFICATION
An endpoint anyone can call.
IGNORING RATE LIMITS
Access suspended at the worst moment.
WHAT ALL OF THESE SHARE
They surface during incidents rather than during development.
