ISSUEWorkflow that is started automatically (by other workflow/scheduled), with an Execute SQL action is failing to run, sometimes with explicit SQL timeout errors, and other times without.
- Copy your SQL query from the Execute SQL action.
- Open SQL Management Studio and run the query against the associated database.
- If the query is taking close to, or longer than 15 seconds, this could result in a SQL timeout.
This issue can be resolved by extending that connection timeout value inside the Execute SQL action. Append Connect Timeout=XX at the end of the connection string. For example:
ADDITIONAL INFORMATIONThe Execute SQL action executes via the .NET framework and there is a built in 15 second timeout value that can cause workflows to fail.