[GH-ISSUE #3441] [BUG]: Invocation of model ID deepseek.r1-v1:0 with on-demand throughput isn’t supported. Retry your request with the ID or ARN of an inference profile that contains this model. #2221

Closed
opened 2026-02-22 18:28:43 -05:00 by yindo · 4 comments
Owner

Originally created by @NameMeLeo on GitHub (Mar 10, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3441

How are you running AnythingLLM?

Docker (local)

What happened?

I got the below output when I am using bedrock with deepseek, its seems that bedrock required a inferenceConfig as below.

Error msg: Invocation of model ID deepseek.r1-v1:0 with on-demand throughput isn’t supported. Retry your request with the ID or ARN of an inference profile that contains this model.

aws sample api query:

{
  "modelId": "deepseek.r1-v1:0",
  "contentType": "application/json",
  "accept": "application/json",
  "body": {
    "inferenceConfig": {
      "max_tokens": 512
    },
    "messages": [
      {
        "role": "user",
        "content": "this is where you place your input text"
      }
    ]
  }
}

Are there known steps to reproduce?

set model ID to deepseek.r1-v1:0 in LLM provider page

No response

Originally created by @NameMeLeo on GitHub (Mar 10, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3441 ### How are you running AnythingLLM? Docker (local) ### What happened? I got the below output when I am using bedrock with deepseek, its seems that bedrock required a inferenceConfig as below. Error msg: Invocation of model ID deepseek.r1-v1:0 with on-demand throughput isn’t supported. Retry your request with the ID or ARN of an inference profile that contains this model. aws sample api query: ```json { "modelId": "deepseek.r1-v1:0", "contentType": "application/json", "accept": "application/json", "body": { "inferenceConfig": { "max_tokens": 512 }, "messages": [ { "role": "user", "content": "this is where you place your input text" } ] } } ``` ### Are there known steps to reproduce? set model ID to ```deepseek.r1-v1:0``` in LLM provider page _No response_
yindo added the possible bug label 2026-02-22 18:28:43 -05:00
yindo closed this issue 2026-02-22 18:28:43 -05:00
Author
Owner

@NameMeLeo commented on GitHub (Mar 12, 2025):

another error from bedrock when using r1 with model id us.deepseek.r1-v1:0

AWSBedrock:streaming - could not stream chat. Unsupported content block type(s): { "reasoningContent": { "text": "Okay" } }
@NameMeLeo commented on GitHub (Mar 12, 2025): another error from bedrock when using r1 with model id ```us.deepseek.r1-v1:0``` ```plaintext AWSBedrock:streaming - could not stream chat. Unsupported content block type(s): { "reasoningContent": { "text": "Okay" } } ```
Author
Owner

@timothycarambat commented on GitHub (Mar 25, 2025):

The original issue - the reason for this is that the proper ID is us.deepseek.r1-v1:0 NOT the one shown in the UI as deepseek.r1-v1:0

Image

Indeed though we need to basically rebuild our Bedrock implementation - as langchain is blocking us from being able to run these newer models and still have them be on parity with other providers.

@timothycarambat commented on GitHub (Mar 25, 2025): The original issue - the reason for this is that the proper ID is `us.deepseek.r1-v1:0` **NOT** the one shown in the UI as `deepseek.r1-v1:0` <img width="1552" alt="Image" src="https://github.com/user-attachments/assets/fdb0c834-ac6e-4343-bf27-5f1f60fbb40c" /> Indeed though we need to basically rebuild our Bedrock implementation - as langchain is blocking us from being able to run these newer models and still have them be on parity with other providers.
Author
Owner

@NameMeLeo commented on GitHub (Mar 25, 2025):

I am using the latest docker image for us.deepseek.r1-v1:0 and now it can use properly, thanks.

@NameMeLeo commented on GitHub (Mar 25, 2025): I am using the latest docker image for us.deepseek.r1-v1:0 and now it can use properly, thanks.
Author
Owner

@timothycarambat commented on GitHub (Mar 26, 2025):

@NameMeLeo apologies that took so long to patch, glad it is working now.

@timothycarambat commented on GitHub (Mar 26, 2025): @NameMeLeo apologies that took so long to patch, glad it is working now.
yindo changed title from [BUG]: Invocation of model ID deepseek.r1-v1:0 with on-demand throughput isn’t supported. Retry your request with the ID or ARN of an inference profile that contains this model. to [GH-ISSUE #3441] [BUG]: Invocation of model ID deepseek.r1-v1:0 with on-demand throughput isn’t supported. Retry your request with the ID or ARN of an inference profile that contains this model. 2026-06-05 14:45:16 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2221