Hey -
Anybody else experiencing this error when trying to search the DB?
“There was an issue retrieving your data.
Database query timeout on “data-panel query””
Yes, more frequent on large (X00 000 row) tables.
Having some other performance issues recently.
Hm, table only has 600 entries…
I’ve been seeing this on Grouped searches…
I’m literally just typing a single field value into the search bar directly in the database… no grouping, 600 entries
same, a lot of entry in db but the search is made in backend, with no filtered… I ve a support ticket running on this.
1 Like
Let me know if you hear anything
Following. It’s happening on a large DB (2M rows) for one of my app
I guess that makes a bit more sense, but still odd. After awhile, I popup the error and the search goes through, but it takes a bit
Response from support : large databases that are constantly being updated are at higher risk of these types of timeout errors due to how database indexing and cleaning work
Just for better clarity, since this is troubling, those experiencing issues what are your estimated list sizes for your Searches (with constraints)?
I’m very particular on the list sizes, or overall estimated data size, returned from any Search. Could be that not having enough constraints and privacy rules are causing these issues.
I got this on a table with 600 total records
I got this error on a table with 600 total records
One tip is that more constraints can help performance (when the constraints aren’t complex themselves).
Suppose we have Projects that belong to a Team and Company (where Teams belong to a Company).
Search for Projects where Team = X and Company = X's Company will be quicker (in theory) than Search for Projects where Team = X even if the results are the same. Generally you wouldn’t notice a difference, but if you’re hitting timeouts, that’s something you could try. Excluding results past a certain date may also help (e.g if you know Company's Created Date, you can include a date > Company's Created Date constraint in the Search for Projects) as it may well help the database query eliminate more results faster.
1 Like
Thanks. I’m still having a difficult time understanding how this error could arise from a table with less than 700 records? Seems like something else is misfiring
Are you storing descriptions from a rich text editor that might contain images? What are your search constraints? What’s your search expression?
No images - although I am storing a decent amount of plain text. The search constraint was simple, just: search for summaries where id = x
ID as in Bubble Unique ID?
No, a separate ID field I’ve created.
Is this search a workflow action or is it contained in a repeating group’s element? Do you have other searches going on while this particular sewrch is happening?
Timeouts usually happen if the search constraints are too broad in a very large database or the data that needs to be returned is very large. This also applies to running multiple searches simultaneously.
I got this error when searching directly in the database on the database tab in Bubble. Wasn’t even running a search.