Symptoms:
Pre HCX 4.3.x deployments.
The causes for a migration workflow to be disrupted and become not actionable can vary and in most cases are unrelated to HCX, due to environmental issues or failure on other components.
If you encounter the symptoms described in this article, please do not hesitate to open a case with Broadcom support. Please reference this Article number (302558) in the case description.
Impact/Risks:
There is a risk to corrupt the HCX database which may render services unusable if the incorrect entries/collections are modified.