# Long idle period kills a functionality

**URL:** <https://forum.inductiveautomation.com/t/long-idle-period-kills-a-functionality/36890>\
**Category:** Ignition\
**Tags:** database, scripting, perspective\
**Created:** [July 21, 2020, 7:05am UTC](https://forum.inductiveautomation.com/t/long-idle-period-kills-a-functionality/36890 "2020-07-21T07:05:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ott.sellis](https://avatars.discourse-cdn.com/v4/letter/o/bbce88/32.png) [@ott.sellis](https://forum.inductiveautomation.com/u/ott.sellis)\
**Post date:** [July 21, 2020, 7:05am UTC](https://forum.inductiveautomation.com/t/long-idle-period-kills-a-functionality/36890/1 "2020-07-21T07:05:27Z")

</div>

Hi,

I have a weird occurence at one of my Perspective projects. We are using Perspective pages on IPCs to reason respective machine downtimes.

The logic is essentially going through the last 24h of the transaction group table and looking where the productive state has gone to 0, taking the following row\_id and binding it to a downtime\_assigned table which binds it to one of multiple selectable reasons.

The weird thing about this is that the logic works fine for some amount of time, but as the page has been idle for a period of time (30 minutes is definitely enough) the insertion of a new row to the downtime\_assigned group stops working although the downtimes binding is being polled every 15 seconds.

Could someone give me some sort of explanation as to why this is happening? or a lead to look for?