Hello GoodData Team, @kapa.ai When I try to create a custom SQL dataset in the GoodData LDM for an object that exists as a view in the Snowflake data source, it results in a timeout error after 30 seconds of execution. This issue does not occur with other regular tables. According to the GoodData documentation, the default timeout is set to 160 seconds. However, the query stops after just 30 seconds. Please help us identify if there is any specific setting we should adjust to increase the timeout limit, or assist us in investigating this issue further. Please refer below SS for reference:

Sorry @Aishwarya K, it looks like your question contains files, which I cannot process. Please reformulate your question without including any files.

Hello GoodData Team, @kapa.ai When I try to create a custom SQL dataset in the GoodData LDM for an object that exists as a view in the Snowflake data source, it results in a timeout error after 30 seconds of execution. This issue does not occur with other regular tables. According to the GoodData documentation, the default timeout is set to 160 seconds. However, the query stops after just 30 seconds. Please help us identify if there is any specific setting we should adjust to increase the timeout limit, or assist us in investigating this issue further.

Hi Aishwarya, Unfortunately the traceID is not very well readable from the screenshot. But anyways. I think it would be best if you send us direct URL into the workspace in question and also share with us the SQL query which you are trying to run. We will check the behavior from our end. Thanks!

Hello Aishwarya, I am wondering if you had a chance to review the reply from my colleague, Julius. Please let us know if you are still facing the issue, and if so, please provide the requested information.

Hello Team, Thanks for your response. please refer below image for the error. please let me know if it is required to post the queries here for further investigation.

Hi Aishwarya, as my colleague mentioned previously: Unfortunately the traceID is not very readable from the screenshot, so please send us the Trace ID by copying and pasting the TraceID directly into this thread, instead of the screenshot. Also, please send us direct URL into the workspace in question and also share with us the SQL query which you are trying to run. Thank you!

here is the trace, Cannot run query, because it is invalid. DB request exception (state=GENERAL_ERROR dataSourceId=6a934468-5567-4aa7-8837-c98bbceb9511 vendorErrorState=GENERAL_ERROR vendorErrorCode=3) General errornet.snowflake.client.jdbc.SnowflakeSQLException: SQL execution canceled (Trace ID: 06d2136f2b0c6eb7a5c623f510405d5d)

Hi Aishwarya, Thank you for providing this information. We checked the logs and this is happening during the short metadata probe that runs when creating a Custom SQL dataset. This probe has a ~30s guardrail on our side — that’s why your view query gets cancelled at ~30s, even though the full execution limit is higher.

Hi Julius, is there any way we can increase this time limit of 30 sec ? i have tried selecting only one column but still faced issue, Applying 1=0 means it will always return empty result set.

Hi Aishwarya, GD Cloud has a hard coded limit for SQL query execution of 30s and cannot be increased. There is currently no supported way to increase the 30-second timeout for the metadata probe when creating a custom SQL dataset. If your view is too complex or slow for this, you will need to simplify the query, reduce the number of columns, or perhaps materialize the view as a table to proceed

ok, thank you!