Does dify support multiple model configurations with the same model name from the same provider?

[ddling]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

When I tried to use Huawei Cloud's MaaS platform, I found that the pre-configured models conflicted with the models I deployed myself because they share the same model name. How can this issue be resolved?

[dosubot[bot]]

Dify does not currently support multiple model configurations with the same model name from the same provider within the same workspace. This is enforced by a unique constraint on the combination of tenant, provider, model name, and model type in the backend, so any attempt to add a duplicate will result in a conflict. There is no built-in alias or alternate name feature to distinguish between such models—this is a known limitation and has been discussed in several issues and feature requests (example, example).

Workarounds suggested by maintainers include using irregular or custom model names, or (for self-hosted deployments) copying the provider code to create a new provider entry, but these are not native solutions. There are ongoing discussions about adding a "Model Alias" field, but as of now, this is not implemented (source).

If you need to use both pre-configured and custom models with the same name, you will need to rename one of them or use a workaround as above.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[ddling]

@dosu using display name can't help to fix the same model id but different endpoint api problem

[dosubot[bot]]

You're right—using a display name doesn't solve the problem because Dify enforces model uniqueness and endpoint mapping based on backend identifiers (tenant, provider, model name, model type), not the display name. The display name is just for UI and has no effect on how requests are routed or how models are distinguished in the backend, so you can't have two models with the same provider and model name even if their endpoints are different (source).

Currently, there's no built-in alias or alternate name feature to work around this. The only options are to use custom/irregular model names or, if you're self-hosting, duplicate the provider code to create a new provider entry (source). There are ongoing discussions about adding a "Model Alias" field to help with this, but it's not implemented yet (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}