That's what I initially thought too, but after talking with the client and ProConnect support, we found out it was the 3rd dependent who was the issue. Not the second one.