Connector Drift
When a connected system changes its API and the integration’s mapping no longer matches reality.
Drift is the gradual or sudden divergence between what an integration expects and what a connected system actually returns. Enterprise systems update their APIs constantly — fields are added, removed, or renamed; endpoints move; versions change.
On a conventional platform, drift is the leading cause of broken integrations and the 2am pages that follow. On Ngentix, drift is a signal the Runtime Monitor watches for: when detected, it triggers the self-healing loop automatically.
Read next.
Self-Healing The ability of an integration to detect when an upstream API changes and repair itself automatically, without human intervention. /glossary/self-healing
Runtime Monitor The subsystem that evaluates every live response, classifies failures, and triggers self-healing or escalation. /glossary/runtime-monitor
Autonomous Connector Creation The process by which the engine discovers, builds, and tests a working connector to a system with no human input. /glossary/autonomous-connector