You are viewing limited content. For full access, please sign in.

Question

Question

custom query timeout not working in a workflow

asked on June 27, 2015 Show version history

I have a workflow with a custom query activity that keeps giving me a timeout error after about 30 seconds. The data connection is an Oracle ODBC DSN. I have some other workflows that connect to this same database and are running just fine. The query that is experiencing the timeout does have a large amount of data to go through and it's expected to return several thousand rows. I disabled the query timeout setting within the ODBC DSN using the odbc manager. I also verified that the query timeout key in the registry shows "F" or false so its disabled. I tried setting the custom query timeout to 1201 seconds within the custom query activity but it still gives a timeout error after about 30 seconds. I applied the latest updates to workflow so am at version 9.2.1.239. Am I missing a setting somewhere? I can run this same query using a sql query tool and it will return results after about 3 minutes. I am attaching screen shots that show how the ODBC DSN is configured and also shows the custom query timeout settings on the actual activity.

I am actually able to run this query successfully when it runs in the actual workflow, I am just not able to test the query in the designer which means that when i try to use tokens returned by the query, they are not available.

ODBC_DSN_Settings_timeout_disabled.png
registry_settings_for_odbc_-_timeout_set_to_false.png
custom_timeout_set_to_1201_seconds.png
0 0

Replies

replied on July 1, 2015

anyone? There has got to be a way to raise the "test query" timeout limits.

0 0
replied on August 24, 2015

Hi Chris,

Thank you for the info and screenshots. This sounds like a bug, and I'll update the thread once we have more information. In the meantime, typing in the tokens is a workaround.

0 0
replied on September 24, 2015

Any update on this? I'm getting a similar error.

0 0
replied on September 25, 2015

Hi Claude,

The issue is being looked at, but I don't have updates yet.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.