https://community.blueprism.com/t5/Product-Forum/SQL-Server-Internal-Timeout-Of-SQL-Queries/m-p/54533#M9037 You might need to use a bespoke connection string that specifies a higher timeout value. On the Set Connection page of the SQL utility object you'll see Calculation stages where the connection string is constructed. Try experimenting with appending ;Connection Timeout=180 Fri, 12 Jan 2018 15:57:00 GMT John__Carter 2018-01-12T15:57:00Z https://community.blueprism.com/t5/Product-Forum/SQL-Server-Internal-Timeout-Of-SQL-Queries/m-p/54532#M9036 We're working with a database that takes up to 2 minutes to respond with results. Blue Prism seem to throw a timeout exception after 30 seconds. I need to be able to override this behavior. Anyone with any input on this very specific problem? Thu, 11 Jan 2018 21:22:00 GMT https://community.blueprism.com/t5/Product-Forum/SQL-Server-Internal-Timeout-Of-SQL-Queries/m-p/54532#M9036 Anonymous 2018-01-11T21:22:00Z https://community.blueprism.com/t5/Product-Forum/SQL-Server-Internal-Timeout-Of-SQL-Queries/m-p/54533#M9037 You might need to use a bespoke connection string that specifies a higher timeout value. On the Set Connection page of the SQL utility object you'll see Calculation stages where the connection string is constructed. Try experimenting with appending ;Connection Timeout=180 Fri, 12 Jan 2018 15:57:00 GMT https://community.blueprism.com/t5/Product-Forum/SQL-Server-Internal-Timeout-Of-SQL-Queries/m-p/54533#M9037 John__Carter 2018-01-12T15:57:00Z