Query timeout is not what I expect and I'm not sure why

💬 Queries and Resources
1
  1. My goal:
    I have a query in my module that previously had a 10s timeout, and I want to bump it to 60s.
  2. Issue:
    I change the timeout to 60s and save, but it doesn't seem to take. I'm attaching a screenshot showing:
  • The query is saved with a 60000ms (60s) timeout
  • I've just run the query and it's failed at just over 10s
  • The error message says "Query timed out at 10.00 seconds"

  1. Steps I've taken to troubleshoot:
    I'm testing directly in the module to rule out versioning issues. I have other queries to this resource with a 60s timeout that work as expected, so this is not a configuration issue with the database or database connection.

  2. Additional info:
    I'm self-hosted on an old version (3.178.0)

2

Oops. The promised screenshot:

image
image1818×1764 361 KB

3

Hey @Mark_Slade - thanks for reaching out and for your patience! It looks like you're importing this query from the Query Library, yeah? If so, the timeout setting in the library itself takes priority over whatever value is set within the app.

image
image1914×632 49.9 KB

This is admittedly a bit confusing and not a great user experience. :sweat_smile: I've documented it as a bug internally and will give you an update as soon as I have news to share!

4

you can change the query timeout from the query library.

these are the step:

1)Go to the Query Library setting.

2)Edit the timeout value 60000 instead of 100000.

3)Save the change.

4)The new timeout will now apply anywhere that query is used.