# 8.0.10 Flood Limit Tripped by SQL Queries

**URL:** <https://forum.inductiveautomation.com/t/8-0-10-flood-limit-tripped-by-sql-queries/34011>\
**Category:** Ignition\
**Tags:** ignition80, perspective, scripting\
**Created:** [April 17, 2020, 2:57pm UTC](https://forum.inductiveautomation.com/t/8-0-10-flood-limit-tripped-by-sql-queries/34011 "2020-04-17T14:57:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![lwood](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@lwood](https://forum.inductiveautomation.com/u/lwood)\
**Post date:** [April 17, 2020, 2:57pm UTC](https://forum.inductiveautomation.com/t/8-0-10-flood-limit-tripped-by-sql-queries/34011/1 "2020-04-17T14:57:08Z")

</div>

Has anyone else seen Perspective cpu spikes/crashes that seem to be caused by flood limit trips that cause clock drifts?

I have a bunch of perspective screens that just call up named queries, nothing really special a few filters and some WHERE IN’s. Opening them in a session seems to start a cascade of flood trips that turn to clock drifts and crash the gateway.

---

<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:** [April 17, 2020, 3:05pm UTC](https://forum.inductiveautomation.com/t/8-0-10-flood-limit-tripped-by-sql-queries/34011/2 "2020-04-17T15:05:40Z")

</div>

Are you sure it has anything to do with the queries? The flood limit should only be tripped when there’s a cycle in your bindings.

---

<div class="post-metadata">

**Author:** ![lwood](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@lwood](https://forum.inductiveautomation.com/u/lwood)\
**Post date:** [April 17, 2020, 3:50pm UTC](https://forum.inductiveautomation.com/t/8-0-10-flood-limit-tripped-by-sql-queries/34011/3 "2020-04-17T15:50:08Z")

</div>

The flood trip only show properties with named query bindings. I removed any refresh binding scripts so I don’t think a loop could be anywhere.

---

<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:** [April 17, 2020, 3:52pm UTC](https://forum.inductiveautomation.com/t/8-0-10-flood-limit-tripped-by-sql-queries/34011/4 "2020-04-17T15:52:52Z")

</div>

Do your queries include properties whose values are then updated with the result of a query? Even indirectly? That would be a cycle.

---

<div class="post-metadata">

**Author:** ![seth.irwin.ext](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@seth.irwin.ext](https://forum.inductiveautomation.com/u/seth.irwin.ext)\
**Post date:** [March 14, 2025, 5:41pm UTC](https://forum.inductiveautomation.com/t/8-0-10-flood-limit-tripped-by-sql-queries/34011/5 "2025-03-14T17:41:43Z")

</div>

lwood Do you remember the fix for this issue?

---

<div class="post-metadata">

**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\
**Post date:** [March 14, 2025, 6:39pm UTC](https://forum.inductiveautomation.com/t/8-0-10-flood-limit-tripped-by-sql-queries/34011/6 "2025-03-14T18:39:58Z")

</div>

I have seen this happen with some ways of doing bindings on datepickers to populate a control. You have to check your date bindings to make sure they can't get into a circular reference.