Originally posted by: TobiasAchterberg
Unfortunately, this is indeed a bug in CPLEX, and a pretty severe one actually. Thanks again for bringing this up.
The fix is pretty simple, but unfortunately there is not an easy work-around for released versions. The bug was introduced with CPLEX 12.5.0.0 and still exists in 12.5.0.1 and the soon to be released 12.5.1.0.
The bug is triggered when a model that contains explicit user cuts or lazy constraints (i.e., not via a callback but via the CPXaddusercuts and CPXaddlazyconstraints) is optimized multiple times.
#CPLEXOptimizers#DecisionOptimization