Yes. If you have already upgraded from the Free Trial to Enterprise and the error is still exactly Databricks-set rate limit of 0, then changing the QPM/TPM limit in the UI is not going to fix it.

I checked the current Databricks documentation and recent Databricks employee responses. This is the key distinction:

Your problem is a Databricks system-level restriction

There are effectively two different limits:

• Your endpoint/user-configured limit — the QPM/TPM values you changed.
• Databricks system-level limit — controlled by Databricks for the workspace/model.

Your error:

PERMISSION_DENIED: The endpoint is temporarily disabled due to a Databricks-set rate limit of 0

means the second one is 0.

Databricks employees have specifically confirmed that this restriction takes precedence over the limits configured in Serving/AI Gateway. So you can set QPM/TPM to a non-zero value and still receive the same 403.check here similar issue