fix: Clarify misleading error message (#891)

This often fails due to RPC provider issues and incorrectly reports that the route is disabled.
across-protocol · Oct 30, 2023 · 2643dab · 2643dab · vercel · Oct 30, 2023
1 parent 7a244e4
commit 2643dab
Showing 1 changed file with 6 additions and 3 deletions.
diff --git a/api/limits.ts b/api/limits.ts
@@ -109,10 +109,13 @@ const handler = async (
     ]);
     // If any of the above fails or the route is not enabled, we assume that the
     if (
-      disabledL1Tokens.includes(l1Token.toLowerCase()) ||
       tokenDetailsResult.status === "rejected" ||
-      routeEnabledResult.status === "rejected" ||
-      !routeEnabledResult.value
+      routeEnabledResult.status === "rejected"
+    ) {
+      throw new InputError(`Unable to query route.`);
+    } else if (
+      !routeEnabledResult.value ||
+      disabledL1Tokens.includes(l1Token.toLowerCase())
     ) {
       throw new InputError(`Route is not enabled.`);
     }