ID:23435 Hold fixing has been running for <run_time_string>. This usually happens when hold fixing requires multiple full-timing analyses.
CAUSE: Long run time during hold fixing.
ACTION: Look for hold violations in the routed or retimed snapshot and verify whether the timing paths are constrained appropriately.