# Help finding a timer script

**URL:** <https://forum.inductiveautomation.com/t/help-finding-a-timer-script/107329>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [June 12, 2025, 3:15pm UTC](https://forum.inductiveautomation.com/t/help-finding-a-timer-script/107329 "2025-06-12T15:15:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjohnson0238](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@mjohnson0238](https://forum.inductiveautomation.com/u/mjohnson0238)\
**Post date:** [June 12, 2025, 3:15pm UTC](https://forum.inductiveautomation.com/t/help-finding-a-timer-script/107329/1 "2025-06-12T15:15:28Z")

</div>

Is there a good way to help me find a timer script that looks to have a hard coded DB table to it?  
That table doesnt exist anymore and causing errors.

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

---

<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:** [June 12, 2025, 3:19pm UTC](https://forum.inductiveautomation.com/t/help-finding-a-timer-script/107329/2 "2025-06-12T15:19:35Z")

</div>

How do you know that error is coming from a script? Store-and-forward operations on `sqlt_data_...` tables are typically entirely internal to the tag historian. Use the tag report tool to find tags that have their storage provider set to `IgnitionHud`.

---

<div class="post-metadata">

**Author:** ![mjohnson0238](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@mjohnson0238](https://forum.inductiveautomation.com/u/mjohnson0238)\
**Post date:** [June 12, 2025, 4:26pm UTC](https://forum.inductiveautomation.com/t/help-finding-a-timer-script/107329/3 "2025-06-12T16:26:58Z")

</div>

I will do that. How can I find where a timer scritp id coming from like these:

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

---

<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:** [June 12, 2025, 4:35pm UTC](https://forum.inductiveautomation.com/t/help-finding-a-timer-script/107329/4 "2025-06-12T16:35:20Z")

</div>

Those logs are coming from scripts that have an explicit `system.util.getLogger("testdtqLibrary")` or similar. Search your projects for the names on the left.

Consider changing all calls to `system.util.getLogger()` to include the result of `system.util.getProjectName()` in the logger name. (I also use [system.reflect.getModulePath()](https://www.automation-pros.com/toolkit/doc/reflection.html#pyobject) for loggers in any project library scripts.)

---

<div class="post-metadata">

**Author:** ![mjohnson0238](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@mjohnson0238](https://forum.inductiveautomation.com/u/mjohnson0238)\
**Post date:** [June 12, 2025, 4:39pm UTC](https://forum.inductiveautomation.com/t/help-finding-a-timer-script/107329/5 "2025-06-12T16:39:30Z")

</div>

> [@pturmel](#):
>
> Search your projects for the names on the left.

Would I search that in my designer or somewhere on the gateway?

---

<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:** [June 12, 2025, 4:42pm UTC](https://forum.inductiveautomation.com/t/help-finding-a-timer-script/107329/6 "2025-06-12T16:42:44Z")

</div>

The designer will only search one project at a time, but can also search in binary project resources. Using `grep` in the gateway filesystem won't search binary resources, but can search the rest of the gateway in one go.
