fix(egress): keep a bad routing configuration from failing the auth module's load

Author: waleedlatif1

apps/sim/lib/oauth/connect-scope.server.ts

@@ -59,6 +59,19 @@ async function runInOAuthCallbackDraftScope<T>(
   return (await inDraftScope)(run)
 }
 
+/**
+ * Whether routing is on, read once while the auth config is built. A routing configuration that
+ * fails to load counts as on, so the connector stays wrapped and the bad configuration surfaces
+ * on its first request like every other routed call, rather than failing the auth module's load.
+ */
+function routingConfiguredAtStartup(): boolean {
+  try {
+    return isOutboundRoutingEnabled()
+  } catch {
+    return true
+  }
+}
+
 /**
  * Wraps a generic OAuth connector's code exchange and identity lookup so their vendor calls
  * leave through the connecting organization's egress gateway. A connector without its own
@@ -68,7 +81,7 @@ async function runInOAuthCallbackDraftScope<T>(
  * A deployment without outbound routing keeps the connector exactly as configured.
  */
 export function withConnectDraftOutboundScope(config: GenericOAuthConfig): GenericOAuthConfig {
-  if (!isOutboundRoutingEnabled()) return config
+  if (!routingConfiguredAtStartup()) return config
   const { providerId, getUserInfo } = config
   const getToken = config.getToken ?? createOutboundCodeExchange(config)
   return {