# 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:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![luc.martin](https://avatars.discourse-cdn.com/v4/letter/l/77aa72/32.png) [@luc.martin](https://forum.inductiveautomation.com/u/luc.martin)\
**Post date:** [November 29, 2022, 2:22pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/1 "2022-11-29T14:22:46Z")

</div>

Since I upgrade to 8.1.22

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/7/7706da5bd43c4bc6ca9be6e5345d212d04df103e.jpeg)

---

<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

---

<div class="post-metadata">

**Author:** ![luc.martin](https://avatars.discourse-cdn.com/v4/letter/l/77aa72/32.png) [@luc.martin](https://forum.inductiveautomation.com/u/luc.martin)\
**Post date:** [November 29, 2022, 2:37pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/3 "2022-11-29T14:37:15Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/c/0c4b5bbee0b45859133b956987339fafb75b631a.jpeg)

---

<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:44pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/4 "2022-11-29T14:44:56Z")

</div>

Thanks, I created a bug ticket for this.

Maybe someone from the Perspective team will chime in later with a hint about why this is happening and whether there is a workaround.

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [November 29, 2022, 3:20pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/5 "2022-11-29T15:20:33Z")

</div>

There are too many places which reference the property tree to narrow this down without an idea of what's being used while the error is occurring. It's a binding somewhere, but the stacktrace provides no insight into the originating resource. I can't even tell if it's a pure binding or perhaps a transform.

---

<div class="post-metadata">

**Author:** ![luc.martin](https://avatars.discourse-cdn.com/v4/letter/l/77aa72/32.png) [@luc.martin](https://forum.inductiveautomation.com/u/luc.martin)\
**Post date:** [November 29, 2022, 3:39pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/6 "2022-11-29T15:39:14Z")

</div>

Thanks and sorry for the inconvenience, this is a complex view with a lot of pure bindings and transforms, but I finally found the sources of this problem.

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [November 29, 2022, 3:40pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/7 "2022-11-29T15:40:38Z")

</div>

Could we get a copy of the View? Replication always improves the speed with which issues get fixed.

---

<div class="post-metadata">

**Author:** ![luc.martin](https://avatars.discourse-cdn.com/v4/letter/l/77aa72/32.png) [@luc.martin](https://forum.inductiveautomation.com/u/luc.martin)\
**Post date:** [November 29, 2022, 3:52pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/8 "2022-11-29T15:52:52Z")

</div>

[IMAGE\_POPUP.zip](https://forum.inductiveautomation.com/uploads/short-url/57IQ6ADg1u1u00XeGMRwOcxMFH9.zip) (26.4 KB)

---

<div class="post-metadata">

**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\
**Post date:** [November 29, 2022, 3:57pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/9 "2022-11-29T15:57:11Z")

</div>

Which version did you upgrade _from_?

---

<div class="post-metadata">

**Author:** ![luc.martin](https://avatars.discourse-cdn.com/v4/letter/l/77aa72/32.png) [@luc.martin](https://forum.inductiveautomation.com/u/luc.martin)\
**Post date:** [November 29, 2022, 4:10pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/10 "2022-11-29T16:10:10Z")

</div>

I was on 8.1.20

---

<div class="post-metadata">

**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\
**Post date:** [November 29, 2022, 4:20pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/11 "2022-11-29T16:20:27Z")

</div>

Thanks, that's useful info for us... There were some changes in 8.1.21 that _might_ be the culprit here. If you did not experience this issue on 8.1.20, then experienced it on 8.1.22, that's more evidence pointing at those changes that we can look into...

---

<div class="post-metadata">

**Author:** ![ynejati](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ynejati/32/6093_2.png) [@ynejati](https://forum.inductiveautomation.com/u/ynejati)\
**Post date:** [November 29, 2022, 8:45pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/12 "2022-11-29T20:45:14Z")

</div>

Hi,

Thanks for letting us know. What did you discover to be the source of this problem? Was it a particular binding on the view that you've provided? Was it just not configured properly? The primary pathway that is resulting in the NPE existed before 8.1.20, so this is why I am asking. Are we certain you were not seeing this on 8.1.20? Does the NPE eventually go away?

I've haven't had any luck replicating the problem with the view you've provided, is there something I'm missing?

Thanks!

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [December 2, 2022, 5:46pm UTC](https://forum.inductiveautomation.com/t/perspective-executionqueue-issue/67028/13 "2022-12-02T17:46:55Z")

</div>

Just wanted to say that we ended up figuring this out, turns out it's pretty straight-forward after all. This NPE happens if you have bidirectional property bindings set up pointing at property paths that can't be resolved. We'll get this fixed in the next release, but you can safely ignore the error, it's not anything to be too concerned about.
