A shared API changes without notice. What should happen?
Uncontrolled interface changeRestore or contain the impact through the authorized technical process, then establish versioning, notification, and compatibility expectations. Treat the interface as a shared commitment.
What to do now
- Identify affected consumers and behavior
- Coordinate safe restoration or adaptation
- Agree interface version and change rules
- Add compatibility verification
When to escalate
Escalate when
The change disrupts critical service or corrupts data.
Who decides
The accountable integration or dependency owner
Example
A field change is versioned and tested with consumers before the old behavior is retired.
Mistake to avoid
Assuming internal APIs do not need change coordination.
Prevent a repeat
Verify dependency completion with the consuming team and test the integrated outcome early enough to act.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Projects
Keep dependency owners, required evidence and dates with linked work records, confirming supported link behavior in the current build. See the platform
Related cases
- How do we prevent interface changes during final testing?Interface stabilization gap
- Can we use a mock to unblock a dependency?Controlled provisional interface
- The project needs an integration, but the API has no documentation. How should we estimate?Unknown interface effort
- The model changed and our AI workflow became less reliable. What do we do?Uncontrolled model-version change