错误信息: No available channel for model gemini-3.1-pro-preview under group default ...

2026年04月11日 07:39 processing

错误信息

错误名称: AI_APICallError 错误信息: No available channel for model gemini-3.1-pro-preview under group default (distributor) (request id: 20260410233830500823427ppHhBD98) 堆栈信息: AI_APICallError: No available channel for model gemini-3.1-pro-preview under group default (distributor) (request id: 20260410233830500823427ppHhBD98) at file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/dist-DWBkLJID.js:1704:11 at async postToApi (file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/dist-DWBkLJID.js:1599:24) at async OpenAICompatibleChatLanguageModel.doStream (file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/dist-MiiZ7jiT.js:452:48) at async wrapStream (file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/store-BX3OZ3o6.js:48641:32) at async fn (file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/store-BX3OZ3o6.js:47507:17) at async file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/store-BX3OZ3o6.js:43861:19 at async _retryWithExponentialBackoff (file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/store-BX3OZ3o6.js:44024:10) at async streamStep (file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/store-BX3OZ3o6.js:47476:109) at async fn (file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/store-BX3OZ3o6.js:47782:5) at async file:///D:/Program%20Files/Cherry%20Studio/resources/app.asar/out/renderer/assets/store-BX3OZ3o6.js:43861:19 错误原因: "[undefined]" 状态码: 503 请求路径: https://www.dmxapi.cn/v1/chat/completions 请求体: { "model": "gemini-3.1-pro-preview-thinking", "user": "[undefined]", "max_tokens": "[undefined]", "temperature": "[undefined]", "top_p": "[undefined]", "frequency_penalty": "[undefined]", "presence_penalty": "[undefined]", "response_format": "[undefined]", "stop": "[undefined]", "seed": "[undefined]", "serviceTier": "[undefined]", "reasoning_effort": "xhigh", "verbosity": "[undefined]", "messages": [ { "role": "user", "content": "我已经配置好了联网工具,bing。请检查你是否可以联网搜索?" } ], "tools": "[undefined]", "tool_choice": "[undefined]", "stream": true, "stream_options": "[undefined]" } 响应首部: { "cache-control": "no-cache", "content-type": "text/event-stream", "date": "Fri, 10 Apr 2026 23:38:30 GMT", "document-policy": "include-js-call-stacks-in-crash-reports", "server": "nginx", "x-rixapi-request-id": "20260411073716665717363hQ4hGtXy" } 响应内容: { "error": { "message": "No available channel for model gemini-3.1-pro-preview under group default (distributor) (request id: 20260410233830500823427ppHhBD98)", "type": "rix_api_error", "param": "", "code": "model_not_found" } } 数据: { "error": { "message": "No available channel for model gemini-3.1-pro-preview under group default (distributor) (request id: 20260410233830500823427ppHhBD98)", "type": "rix_api_error", "param": "", "code": "model_not_found" } }

AI 解决方案

报错分析报告

1.错误翻译


原文:No available channel for model gemini-3.1-pro-preview under group default (distributor) (request id: 20260410233830500823427ppHhBD98)
译文:在默认分组(分发者)下,模型gemini-3.1-pro-preview没有可用通道(请求ID:20260410233830500823427ppHhBD98)

2. 原因分析


  • 根本原因:请求的模型gemini-3.1-pro-preview在DMXAPI平台默认分组中未配置可用通道(或模型名称与实际调用不匹配)。

  • 具体位置:API调用时model参数值(gemini-3.1-pro-preview-thinking)与错误信息中的模型名(gemini-3.1-pro-preview)不一致,或该模型未在平台启用。
  • 3.解决方案


    修正请求体中的model参数为平台支持的准确名称(需与平台配置的模型名一致):
    // 修复后的请求体(示例:使用平台已启用的模型名)
    {
      "model": "gemini-3.1-pro-preview", // 或确认平台支持的准确模型名(如原意图是thinking版则核对平台是否提供)
      "messages": [{"role": "user", "content": "我已经配置好了联网工具,bing。请检查你是否可以联网搜索?"}],
      "stream": true,
      "reasoning_effort": "xhigh"
      // 移除未定义的字段(如user、max_tokens等)
    }
    

    注:需先通过DMXAPI控制台或模型列表接口确认gemini-3.1-pro-preview或其变体(如gemini-3.1-pro-preview-thinking)是否已启用并分配通道。

    4.️ 预防措施


  • 前置验证:调用API前,用平台提供的「模型列表接口」校验目标模型是否存在于默认分组。

  • 配置同步:统一模型名称配置(如代码中用常量定义模型名),避免拼写错误或版本混淆。

  • 工具推荐:使用Postman或curl先测试模型调用的可用性,再集成到业务代码。