Why This Matters
When two KIPU instances are on different versions — for example, one on V3 and one on V4 — connecting both to Dazos CRM causes a version-switching conflict. The integration endpoint cannot communicate cleanly with two different KIPU versions simultaneously, and the connection breaks down for both instances, not just the mismatched one.
This is not a timing issue. Integrating one instance first and adding the second instance later does not resolve the conflict. As soon as the second instance on a different version is connected, communication breaks for both.
What Happens in Each Scenario
Both instances on the same version: Integration works correctly for both instances.
Instances on different versions (e.g., one V3, one V4): The first instance may work briefly on its own, but once the second instance is connected, version-switching conflicts cause the connection to break for both instances.
Attempting to integrate at different times: This does not work around the version requirement. The conflict occurs the moment the second instance on a different version is added to the same connection.
How to Resolve a Version Mismatch
Identify which KIPU instances are on V3 and which are on V4.
Contact KIPU support and request that any V3 instances be upgraded to V4.
Once all instances are confirmed to be on the same KIPU version, contact Dazos Support to proceed with the multi-instance integration setup.
⚠️ Note: Dazos Support cannot complete the multi-instance integration until all KIPU instances are on the same version. The upgrade must be handled by KIPU directly.
Tips & Notes
💡 Tip: If your organization needs to continue operating while waiting for a version upgrade, Dazos can integrate a single KIPU instance in the meantime. The remaining instance can be added once the version mismatch is resolved.
✅ Best Practice: Before requesting a multi-instance KIPU integration with Dazos, confirm with your KIPU administrator that all instances are on the same version to avoid delays.