# Capturing/Logging Failed Bindings (without script transforms/binding only) in Perspective

**URL:** <https://forum.inductiveautomation.com/t/capturing-logging-failed-bindings-without-script-transforms-binding-only-in-perspective/116755>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [August 11, 2026, 7:09pm UTC](https://forum.inductiveautomation.com/t/capturing-logging-failed-bindings-without-script-transforms-binding-only-in-perspective/116755 "2026-08-11T19:09:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aafabiano01](https://avatars.discourse-cdn.com/v4/letter/a/e8c25b/32.png) [@aafabiano01](https://forum.inductiveautomation.com/u/aafabiano01)\
**Post date:** [August 11, 2026, 7:09pm UTC](https://forum.inductiveautomation.com/t/capturing-logging-failed-bindings-without-script-transforms-binding-only-in-perspective/116755/1 "2026-08-11T19:09:28Z")

</div>

In production, we have an intermittent issue of bindings failing. The binding in question uses a parameter passed to the popup to build a tagpath for reference in an expression tag binding.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/d/edc409ae21967b870b80d1102e8fc8d0ed989e36.png)

In this screenshot, I am replicating this failure in a very simple test screen. tagPath is not being correctly passed into this view. A binding on a label dependent on that tagPath fails because the tagPath is invalid. A red overlay and hoverable error are generated.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/2/723154e63fd06cab6b6ff78d894f97d956d504d5.png)

It would be much easier for us to fix these issues if this was logged anywhere, but currently, our only report/record of these failed bindings is reports from operators. To us, it appears that this error only exists within a single Perspective session at the time of its viewing and then is completely lost on refresh/reevaluation.

We thought of putting a script transform on the binding. However, given that our program is widely distributed, and using a script transform for a single instance of logging when this issue is happening across multiple popups and locations seems very high maintenance, we were wondering if there was a more efficient way of monitoring non-script, non-query failures on these script bindings.

1. Is there any way/where this failure is logged in Ignition, without having to change anything? (Can we currently check something in Ignition to find this issue from a short time ago?)
2. If this is not currently logged, what is the minimum "work" we would have to do to enable this logging/record of failure for future reference? Is there any way we could log this for all binding failures?

Thanks

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 11, 2026, 9:42pm UTC](https://forum.inductiveautomation.com/t/capturing-logging-failed-bindings-without-script-transforms-binding-only-in-perspective/116755/2 "2026-08-11T21:42:38Z")

</div>

Alter the troublesome expressions nest within my Integration Toolkit's [debugMe()](https://www.automation-pros.com/toolkit/doc/debugging.html#debugme) expression function. Use the MDC key parameter to help you pick out the results in Ignition's logging infra.

But note that you cannot trap the quality problems of a tag binding--those are not exceptions, but simply bad quality. For that, you want to use the [qualityOf()](https://www.docs.inductiveautomation.com/docs/8.3/appendix/expression-functions/advanced/qualityOf) function in a separate property. Perhaps with overlay opt-out in the tag binding.