That makes sense.
SolveDistanceConstraint in CableComponent.cpp has a divide by zero if the current distance between two particles in the cable is zero. There is no error or warning because the positions simply turn to NaN. You can see this with a call to GetCableParticleLocations. These NaNs can then only be removed by reinitializing the particle locations, which happens in UCableComponent::OnRegister.
Setting the desired cable length to a non-zero value makes it less likely for the cable to disappear, but it can still happen, especially if there’s no forces on the cable.