From e3f3b675ff472d85d223713a43091910a680bc2a Mon Sep 17 00:00:00 2001 From: Matteo Date: Tue, 16 Jun 2026 12:26:16 +0200 Subject: [PATCH] fix(connectors): apply db-rest host swap to in-app Run Test (executeConnectorCall) The per-tool 'Run Test' in the UI calls executeConnectorCall, which built the engine config from the raw connector.baseUrl (public v6.db.transport.rest). In cloud that public instance is unreachable, so the test hung until the 30s timeout ('Running...' forever). Route it through resolveInternalDbRestUrl like the MCP execution and Test-connection paths so it hits the internal db-rest. --- packages/backend/src/connectors/connectors.service.ts | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/packages/backend/src/connectors/connectors.service.ts b/packages/backend/src/connectors/connectors.service.ts index 20abf3c..ffb2972 100644 --- a/packages/backend/src/connectors/connectors.service.ts +++ b/packages/backend/src/connectors/connectors.service.ts @@ -349,7 +349,10 @@ export class ConnectorsService { : undefined; const config = { - baseUrl: connector.baseUrl, + // Apply the cloud db-rest host swap so the in-app "Run Test" hits the + // real (internal) endpoint, same as MCP tool execution — otherwise it + // calls the public base URL and hangs/times out. + baseUrl: resolveInternalDbRestUrl(connector.baseUrl), authType: connector.authType, authConfig, headers: connector.headers as Record,