# 2 sessions, but 4 queries

**URL:** <https://forum.inductiveautomation.com/t/2-sessions-but-4-queries/98530>\
**Category:** Ignition\
**Tags:** ignition78, database, scripting, vision\
**Created:** [November 12, 2024, 6:01pm UTC](https://forum.inductiveautomation.com/t/2-sessions-but-4-queries/98530 "2024-11-12T18:01:36Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [November 21, 2024, 10:39am UTC](https://forum.inductiveautomation.com/t/2-sessions-but-4-queries/98530/27 "2024-11-21T10:39:55Z")

</div>

The error seems to be,

```python
SQLNestedException: Cannot get a connection, 
pool error Timeout waiting for idle object

```

A web search for that error gives many results including some on this site. See here, for example:

> [@Error database connection](https://forum.inductiveautomation.com/t/error-database-connection/82085/5):
>
> Right at the top: Cannot get a connection, pool error Timeout waiting for idle object This isn't an error on the database side, strictly speaking. Ignition makes multiple internal connections to your DB and recycles them as each query completes. The number and behavior of this "connection pool" is part of the advance settings on a database connection. Not getting a connection for this timeout means you are running more simultaneous long queries than your DB can handle. Either your queries …

---

_[View the full topic](https://forum.inductiveautomation.com/t/2-sessions-but-4-queries/98530)._