@Universeb could you add your cloud, region and workspace tier, please? The published rate limits depend on the tier, so they don't establish your workspace's assigned quota.

For one failed REST call, please include the UTC timestamp, any request ID, and sanitised error details -particularly limit and current, if returned. Those fields would help distinguish usage exhaustion from an unexpectedly low allowance. I'd ask Databricks to check that before switching to provisioned throughput.

Thanks. I reproduced the issue again via the REST API.

Environment:
- Cloud: AWS
- Region: Seoul (ap-northeast-2)
- Workspace tier: Enterprise

Test:
- Model: databricks-deepseek-v4-1-flash
- Prompt: "hi"
- No concurrent workload against this model
- HTTP status: 429
- UTC timestamp: 2026-09-25 22:54:35 UTC
- Request ID: b03cbf14-6dee-49d0-abfe-2e70e9450005

Raw response body:

{"error_code":"REQUEST_LIMIT_EXCEEDED","message":"REQUEST_LIMIT_EXCEEDED: Exceeded workspace input tokens per minute rate limit for databricks-deepseek-v4-1-flash. Please use a provisioned throughput Foundation Model APIs endpoint for a higher rate limit."}

Relevant response headers:

HTTP/1.1 429 Too Many Requests
date: Fri, 25 Sep 2026 22:54:35 GMT
x-request-id: b03cbf14-6dee-49d0-abfe-2e70e9450005

There were no limit/current/retry-after values returned in either the response body or the relevant response headers.

The REST request used only a minimal "hi" prompt. The same issue also reproduces in AI Playground, while other Databricks-hosted foundation models work normally.

One additional detail that may be relevant: DeepSeek V4.1 Flash previously worked successfully for me, but later started consistently returning this workspace ITPM error.

Please let me know if there is any other diagnostic information I can provide.

Thanks, @Universeb. One region-specific detail: Databricks lists DeepSeek V4.1 Flash in ap-northeast-2 as requiring cross-Geo routing, with availability also dependent on GPU capacity.

Could your account admin check Account Console > Workspaces > your workspace > Security and compliance? "Enforce data processing within workspace Geography for Designated Services" needs to be off to allow cross-Geo processing. Please only change it if your data-residency policy permits.

Thanks. I checked that setting.

"Enforce data processing within workspace Geography for Designated Services"

was already disabled when I reproduced the issue, so cross-Geo processing was allowed.

DeepSeek V4.1 Flash still returned the same ITPM 429 in both AI Playground

and the REST API.

REST reproduction:

- Cloud: AWS

- Region: Seoul (ap-northeast-2)

- Workspace tier: Enterprise

- HTTP status: 429

- UTC timestamp: 2026-09-25 22:54:35 UTC

- Request ID: b03cbf14-6dee-49d0-abfe-2e70e9450005

Response:

REQUEST_LIMIT_EXCEEDED: Exceeded workspace input tokens per minute rate limit for

databricks-deepseek-v4-1-flash.

No limit, current, or retry-after values were returned.