# Violation set timeout error

**URL:** <https://forum.inductiveautomation.com/t/violation-set-timeout-error/98455>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [November 11, 2024, 7:32am UTC](https://forum.inductiveautomation.com/t/violation-set-timeout-error/98455 "2024-11-11T07:32:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dharani\_T](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@Dharani\_T](https://forum.inductiveautomation.com/u/Dharani_T)\
**Post date:** [November 11, 2024, 7:32am UTC](https://forum.inductiveautomation.com/t/violation-set-timeout-error/98455/1 "2024-11-11T07:32:47Z")

</div>

In Ignition, I use the following:

- `query = procedure to fetch data`
- `table.data = query result`
- `params.Data = query result`

When the query result has more than 5000 rows, there's no issue binding it to the table (even when results \> 50K). However, binding it to the `Data` parameter results in a 'Lost connection to gateway' error along with a `[Violation] 'setTimeout'` error.

---

<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:** [November 11, 2024, 12:58pm UTC](https://forum.inductiveautomation.com/t/violation-set-timeout-error/98455/2 "2024-11-11T12:58:29Z")

</div>

Yup, don't pass large datasets as view parameters. They cannot be optimized before transmission like component native properties.

Consider storing the raw dataset in a [pageVarMap()](https://www.automation-pros.com/toolkit/doc/scripting.html#pagevarmap), where each view can access it without passing through the browser.