# \[IGN-9937\]Run Diagnostics at Template Level

**URL:** <https://forum.inductiveautomation.com/t/ign-9937-run-diagnostics-at-template-level/90684>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 21, 2024, 2:53pm UTC](https://forum.inductiveautomation.com/t/ign-9937-run-diagnostics-at-template-level/90684 "2024-05-21T14:53:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [May 21, 2024, 2:53pm UTC](https://forum.inductiveautomation.com/t/ign-9937-run-diagnostics-at-template-level/90684/1 "2024-05-21T14:53:42Z")

</div>

The run diagnostics feature has been very useful for me recently. However, there are many times that customer internal properties for a template are at the root template level and there's no way to run diagnostics at that level.

> **[Run Diagnostics Root Container | Ignition Features and Ideas | Inductive...](https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/run-diagnostics-root-container)**
>
> Add the run diagnostics right-click option at the root container/template level.