# Unsupported constraint only in infeasibility analysis

**URL:** <https://discourse.julialang.org/t/unsupported-constraint-only-in-infeasibility-analysis/135721>\
**Category:** Optimization (Mathematical)\
**Tags:** question, gurobi\
**Created:** [February 18, 2026, 10:43am UTC](https://discourse.julialang.org/t/unsupported-constraint-only-in-infeasibility-analysis/135721 "2026-02-18T10:43:33Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ohmsweetohm1](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ohmsweetohm1/32/49126_2.png) [@ohmsweetohm1](https://discourse.julialang.org/u/ohmsweetohm1)\
**Post date:** [February 18, 2026, 7:22pm UTC](https://discourse.julialang.org/t/unsupported-constraint-only-in-infeasibility-analysis/135721/5 "2026-02-18T19:22:51Z")

</div>

So MathOptAnalyzer is not dispatching to compute\_conflict! if the solver supports it?

---

_[View the full topic](https://discourse.julialang.org/t/unsupported-constraint-only-in-infeasibility-analysis/135721)._