MS SQL Server Database Connection

[redhat00]

Hey Retool.

We have been using Retool for over a year to run queries on our MS SQL instance.We only recently been getting this new error:

We have seen other errors like it. But this one looks different.

It seems like when a Workflow encounters this error, it doesn’t even try to rerun the query even though we set it to do that. It happens quite frequently in every app and Workflow.

Could this be an issue with the nodejs driver?

Thanks so much, Retool!

``
{
"error": {
"statusCode": 422,
"error": "Unprocessable Entity",
"message": "Failed to connect to 12.12.12.12:1212 in 15000ms",
"data": null,
"isRetoolSystemError": false,
"queryExecutionMetadata": {
"estimatedResponseSizeBytes": 151,
"resourceTimeTakenMs": 15003,
"isPreview": false,
"resourceType": "mssql",
"lastReceivedFromResourceAt": 1761594786537
}
},
"data": null,
"value": null,
"metadata": null
}
``

[Darren]

Thanks for joining Office Hours today, @redhat00! I will spend some more time digging into this, but it feels like you're potentially exhausting the number of connect slots on the resource. Do you have access to Cato logs that might be able to verify this?

[redhat00]

Its hard to parse granular data and our VPN provider cannot show there is trouble on their end.

It seems possible that TCP connections or sessions are getting created by Retool and never going away. Like the session is in infinite sleep status.