Setting query timeout for the database (in our case postgres) would be useful, so that the DB times out a query if it runs longer than Klipfolio timeout.
Date
Votes
7 comments
-
Juho-Pekka,
I am interested to know more about your use case and the challenges you are running into.
- Why do you want to stop the query on your end?
- Would increasing the Klipfolio timeout help solve your problem?
Thanks!
-
The issue is twofold:
- the current timeout for Klipfolio queries is too short for some of the queries. Our solution has been to make materialized views of those, but it's a but clumsy.
- If a klipfolio query times out, the database still keeps executing the query. Sometimes it happens the query slows down other queries which creates a cascading effect of more and more queries timing out. If the Klipfolio db connector set the same timeout for the db queries as it is for the app, the db queries wouldn't be needlessly running.
-
I understand. Makes total sense.
We are working on a feature (as an add-on) in the labs to increase the timeout and support longer running queries. Would you be interested in being on the waiting list for the feature and give it try as a beta user?
-
Sure.
-
Great! we'll be in touch soon!
-
Ali, I am also having a timeout issue with Salesforce. I repeatedly have run into the timeout issues when creating datasources (prayerfully it hasn't affected the actual Klips and dashboards).
It's an intermittent issue for me---but stops our development team dead in our tracks when we hit it and there is NOTHING customer service can do about it. You can reference ticket #95836 and 96268.
In our case our SOQL statement is incredibly simple:
select CloseDate, Amount, AccountId from Opportunity where IsWon = TRUE and CloseDate >= LAST_N_MONTHS:12 Order by CloseDate
It returns about 69K rows and is about 3 megabytes. I was told the timeout is 80 seconds. Can you inform me on this topic? Is it the same issue as Juho's?
Thanks for your clarification and please add me to this beta ASAP.
-
Brian,
Saleforce response times to our platform can be inconsistent, which is why sometimes your datasource creation works and sometimes it doesn't. For existing salesforce datasources, we've actually extended the timeouts under the covers to 200 seconds to prevent datasources from being disabled unnecessarily, but this doesn't apply to the setup stage. We're currently evaluating options in allowing longer timeouts for datasource setup, and will be working on providing this in the near future.
Thanks for the feedback!
Please sign in to leave a comment.