Hello Deno team,I'm hoping you can help me with a persistent deployment failure on Deno Deploy. I'm trying to deploy a very simple API middleware server that takes a JSON request, converts it to XML, and forwards it to an external API. The code works perfectly when run locally.However, every deployment attempt fails with ISOLATE_INTERNAL_FAILURE immediately after the "Packaging complete" step in the build logs. I am fairly confident this is a platform-level issue, as I have exhausted all the troubleshooting steps I can think of.My Deno Deploy project name is: salesforce-middlewareCodeHere is the complete code for the project.main.ts// main.ts import { serve } from "https://deno.land/std@0.217.0/http/server.ts"; import { XMLParser, XMLBuilder } from "npm:fast-xml-parser"; // --- Configuration and Credentials --- const EMERCHANTPAY_URL = 'https://staging.wpf.emerchantpay.net/en/wpf'; const empUsername = Deno.env.get("EMP_USERNAME"); const empPassword = Deno.env.get("EMP_PASSWORD"); // --- Pre-flight Check --- if (!empUsername || !empPassword) { console.error("CRITICAL STARTUP ERROR: EMP_USERNAME or EMP_PASSWORD is not defined."); console.error("The server will not start processing requests until these environment variables are set."); } else { console.log(`✅ Middleware server starting...`); serve(async (req: Request) => { const url = new URL(req.url); if (url.pathname !== '/' || req.method !== 'POST') { return new Response("Not Found", { status: 404 }); } try { const salesforceJson = await req.json(); const objectForXml = { wpf_payment: { ...salesforceJson, transaction_types: { transaction_type: { '#text': '', '@_name': 'sale' } } } }; const builder = new XMLBuilder({ format: true, ignoreAttributes: false, }); const xmlPayload = builder.build(objectForXml); const authHeader = `Basic ${btoa(`${empUsername}:${empPassword}`)}`; const empResponse = await fetch(EMERCHANTPAY_URL, { method: 'POST', headers: { 'Content-Type': 'application/xml', 'Authorization': authHeader, }, body: xmlPayload, }); const emerchantPayXmlResponse = await empResponse.text(); if (!empResponse.ok) { throw new Error(`eMerchantPay returned status ${empResponse.status}`); } const parser = new XMLParser({ignoreAttributes: false}); const jsonForSalesforce = parser.parse(emerchantPayXmlResponse); return new Response(JSON.stringify(jsonForSalesforce), { headers: { 'Content-Type': 'application/json' }, status: 200, }); } catch (error) { const errorMessage = error instanceof Error ? error.message : "Unknown error"; console.error("An error occurred in the middleware:", errorMessage); return new Response( JSON.stringify({ status: "error", message: "Middleware processing failed.", details: errorMessage, }), { headers: { 'Content-Type': 'application/json' }, status: 500, } ); } }); } deno.jsonc{ "tasks": { "start": "deno run --allow-net --allow-env main.ts", "dev": "deno run --watch --allow-net --allow-env main.ts" }, "compilerOptions": { "lib": ["deno.window"], "moduleResolution": "bundler" } } Build LogThis is the build log every time, regardless of the troubleshooting steps taken:Build Logs Downloaded file:///src/main.ts (1/2) Downloaded https://deno.land/std@0.217.0/http/server.ts (2/3) Downloaded https://deno.land/std@0.217.0/async/delay.ts (3/3) Packaging complete The deployment failed: ISOLATE_INTERNAL_FAILURE Troubleshooting Steps Already TakenI have tried all of the following, and each one results in the same ISOLATE_INTERNAL_FAILURE:Removed Forbidden APIs: My code does not use Deno.exit() or other system-level APIs forbidden in Deno Deploy.Removed dotenv: I removed the dotenv dependency to simplify the dependency graph, relying only on environment variables injected by the platform.Aligned std versions: I tried aligning all deno.land/std imports to the same latest version (0.224.0).Used Older std version: I reverted the std library version to a known-stable older version (0.217.0), which is reflected in the code above.Removed deno.jsonc: I tried deploying without a deno.jsonc file entirely to rule out a configuration issue.Could you please take a look or let me know if there's a known platform issue that might be causing this? Any help would be greatly appreciated!