# Perspective - ExecutionQueue issue

**URL:** <https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028>\
**Category:** Ignition Early Access\
**Tags:** ignition81, perspective\
**Created:** [November 29, 2022, 2:22pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028 "2022-11-29T14:22:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [November 29, 2022, 2:28pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/2 "2022-11-29T14:28:04Z")

</div>

Any chance you can restart the gateway with this additional parameter added and then post the logs with the full stack trace?

> [@\[BUG-6826\]: Change notification error flooding the log after updating to 8.1.22](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/7):
>
> If this is a test environment, any chance you can add the following line to your data/ignition.conf file under the # Java Additional Parameters heading (updating the number 6 if necessary)? wrapper.java.additional.6=-XX:-OmitStackTraceInFastThrow On restart, in theory, it should start providing a stack trace. Thanks, Garth

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028)._