Enhance the error handling and retry logic for the move contact feature to ensure robustness in cases of connectivity loss or other interruptions.
Background
During heavy move operations, it is common to encounter connectivity issues which can interrupt the cht-conf process. Currently, if a contact move job fails due to lost connectivity, the job needs to be manually retried from the board. While cht-conf can aggregate documents and retry the move, cht-user-management does not allow retrying an aborted job if the top-level contact has already been moved.
References
Original discussion on handling interrupted contact moves: (thread)
Description
Enhance the error handling and retry logic for the move contact feature to ensure robustness in cases of connectivity loss or other interruptions.
Background
During heavy move operations, it is common to encounter connectivity issues which can interrupt the
cht-confprocess. Currently, if a contact move job fails due to lost connectivity, the job needs to be manually retried from the board. Whilecht-confcan aggregate documents and retry the move,cht-user-managementdoes not allow retrying an aborted job if the top-level contact has already been moved.References