From 8d678c27f54e3f1de35eb870e8d78afe10d6dfbf Mon Sep 17 00:00:00 2001 From: Waleed Latif Date: Thu, 9 Apr 2026 15:52:57 -0700 Subject: [PATCH] fix(tools): pass errorExtractor to extractErrorMessage and handle proxy error format The executor was calling extractErrorMessage without the tool's errorExtractor ID, so the tool-specific extractor was never used. Also add fallback for the internal proxy route error format ({ error: "..." }) which none of the Atlassian-specific patterns matched. --- apps/sim/tools/utils.server.ts | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/apps/sim/tools/utils.server.ts b/apps/sim/tools/utils.server.ts index c4e06cf94b..e5058eeb64 100644 --- a/apps/sim/tools/utils.server.ts +++ b/apps/sim/tools/utils.server.ts @@ -61,11 +61,14 @@ export async function executeRequest( } } - const error = extractErrorMessage({ - status: resolvedResponse.status, - statusText: resolvedResponse.statusText, - data: errorData, - }) + const error = extractErrorMessage( + { + status: resolvedResponse.status, + statusText: resolvedResponse.statusText, + data: errorData, + }, + tool.errorExtractor + ) logger.error(`${toolId} error:`, { error }) throw new Error(error) }