Error: Cannot connect to detaspace service during migration

When attempting to migrate a lightweight application to detaspace, the migration tool emits the following error:

Error: Cannot connect to detaspace service

The primary objective is to achieve a zero‑downtime transition, preserving user sessions and data integrity. However, the documentation for detaspace does not clearly state whether the platform supports live data replication or staged cutover for small applications.

Key constraints include limited visibility into detaspace’s internal replication mechanisms, uncertainty about how connection failures are handled during a cutover, and the need to maintain consistency across the source and target environments.

To move forward, I need to understand the following:

• Does detaspace provide a documented zero‑downtime migration path for small applications?
• What is the recommended sequence of steps to minimize or eliminate service interruption?
• How can I ensure data consistency if the connection error occurs mid‑migration?