# This page documents known bugs in Dynare stable.
# This page documents known bugs in Dynare stable.
* The `discretionary_policy` command does not accept the `planner_discount_latex_name` option, contrary to what the documentation says (bug fixed in preprocessor@f7917e9bd4369f25a20ce81e617014fdfe4f5718)
* The `outfile` option of the `smoother2histval` command would produce an incorrect file on models with two lags or more, leading to incorrect results when loading that file with `histval_file` (bug fixed in 618712ad9fb9a128545ae9ee8ca01ca2900a3af9)
* The `outfile` option of the `smoother2histval` command would produce an incorrect file on models with two lags or more, leading to incorrect results when loading that file with `histval_file` (bug fixed in 618712ad9fb9a128545ae9ee8ca01ca2900a3af9)
* The point forecasts triggered by `forecast` option of `estimation` did not take shock uncertainty into account (bug not yet fixed, see https://git.dynare.org/Dynare/dynare/-/merge_requests/2384)
* The point forecasts triggered by `forecast` option of `estimation` did not take shock uncertainty into account (bug not yet fixed, see https://git.dynare.org/Dynare/dynare/-/merge_requests/2384)
* Using the `forecast` command with a model solved at `order=2` with `varexo_det`, Dynare would return uncertainty bands based on a first-order approximation (bug not fixed, see #1940)
* Using the `forecast` command with a model solved at `order=2` with `varexo_det`, Dynare would return uncertainty bands based on a first-order approximation (bug not fixed, see #1940)
