<h3>Example case</h3>

<p>The following question </p>

<p><a href="https://stats.stackexchange.com/questions/224749/unable-to-resolve-the-following-parameters-jags-error-for-latent-class-model">&quot;Unable to resolve the following parameters:&quot; jags error for Latent Class Model</a></p>

<p>is a question that is more than two years old now. It has just been bumped up by community for the reason </p>

<blockquote>
  <p>This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. </p>
</blockquote>

<p>The problem with that question is:</p>

<ol>
<li><p>It is not very easy to understand the exact problem (possibly on the edge of off-topic because it is sort of debugging, the underlying problem might be statistical but it is not stated in an explicit clear way)</p></li>
<li><p>The original poster has not been on the website since more than two years.</p></li>
</ol>

<hr>

<h3>Question</h3>

<p>How should we deal with such paralyzed questions? </p>

<ul>
<li>On the one hand I might think that closing and deletion is the only way to 'finish' such questions because the original poster is unlikely gonna be around to accept answers or provide further information on the question (e.g. explain ambiguities, clarify text, provide original data, provide code example/output, etc.) </li>
<li>On the other hand sometimes those questions may contribute to the site, and they are only not very pretty or clearly written.</li>
</ul>

<p>In more general terms (I do not necessarily wish to discuss the particular question which might lead to a simple answer 'just close it')</p>
