Model Provider management stuck in a broken status #8119

Closed
opened 2026-02-21 18:24:03 -05:00 by yindo · 2 comments
Owner

Originally created by @DavideDelbianco on GitHub (Feb 10, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  • Add a Cohere key
  • Open the Cohere models tab and select "add model"
  • Input valid data, for example:
    model type: Rerank
    model name: rerank-v3.5
    Use another valid API Key

From the model "setup" click "remove key"

I suppose it is something related to the Load Balancing feature being configured, but not accessible from CE edition remaining unmanageable

✔️ Expected Behavior

The model provider should be removed

Actual Behavior

The model provider remains

Originally created by @DavideDelbianco on GitHub (Feb 10, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce - Add a Cohere key - Open the Cohere models tab and select "add model" - Input valid data, for example: model type: Rerank model name: rerank-v3.5 Use another valid API Key From the model "setup" click "remove key" I suppose it is something related to the Load Balancing feature being configured, but not accessible from CE edition remaining unmanageable ### ✔️ Expected Behavior The model provider should be removed ### ❌ Actual Behavior The model provider remains
yindo added the 🐞 bug label 2026-02-21 18:24:03 -05:00
yindo closed this issue 2026-02-21 18:24:03 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Feb 10, 2025):

The issue you're experiencing with the model provider management being stuck in a broken status might be related to the conditions required for the successful execution of the deleteModelProvider function. Here are a few things to check:

  1. User Permissions: Ensure that the user attempting to remove the model provider has the necessary permissions. The user must be an admin or owner to perform this action [1].

  2. Edition Restrictions: Since you mentioned using the Community Edition (CE), it's possible that certain features related to model provider management, such as Load Balancing, might not be fully accessible or manageable in this edition. The Dify codebase differentiates between editions using decorators and feature checks, which might restrict certain operations in the CE [2].

  3. Request Parameters: Verify that the request to remove the model provider includes all required parameters, such as model and model_type, and that these parameters are valid [1].

  4. State Management: The remove_provider_credentials method in the ModelProviderService class is responsible for removing provider credentials. Ensure that this method is being called correctly and that the provider configuration exists [3].

If these conditions are met and the issue persists, it might be necessary to further investigate the specific implementation details or logs to identify any underlying problems.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Feb 10, 2025): <!-- Answer --> The issue you're experiencing with the model provider management being stuck in a broken status might be related to the conditions required for the successful execution of the `deleteModelProvider` function. Here are a few things to check: 1. **User Permissions**: Ensure that the user attempting to remove the model provider has the necessary permissions. The user must be an admin or owner to perform this action <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/controllers/console/workspace/models.py)</sup>. 2. **Edition Restrictions**: Since you mentioned using the Community Edition (CE), it's possible that certain features related to model provider management, such as Load Balancing, might not be fully accessible or manageable in this edition. The Dify codebase differentiates between editions using decorators and feature checks, which might restrict certain operations in the CE <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/controllers/console/wraps.py)</sup>. 3. **Request Parameters**: Verify that the request to remove the model provider includes all required parameters, such as `model` and `model_type`, and that these parameters are valid <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/controllers/console/workspace/models.py)</sup>. 4. **State Management**: The `remove_provider_credentials` method in the `ModelProviderService` class is responsible for removing provider credentials. Ensure that this method is being called correctly and that the provider configuration exists <sup>[[3]](https://github.com/langgenius/dify/blob/main/api/services/model_provider_service.py)</sup>. If these conditions are met and the issue persists, it might be necessary to further investigate the specific implementation details or logs to identify any underlying problems. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/26b4a96f-aea0-4936-ace4-60a39a7f3a9c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/26b4a96f-aea0-4936-ace4-60a39a7f3a9c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/26b4a96f-aea0-4936-ace4-60a39a7f3a9c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/26b4a96f-aea0-4936-ace4-60a39a7f3a9c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/26b4a96f-aea0-4936-ace4-60a39a7f3a9c?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/26b4a96f-aea0-4936-ace4-60a39a7f3a9c?feedback_type=other)</sup>
Author
Owner

@crazywoola commented on GitHub (Mar 7, 2025):

@crazywoola commented on GitHub (Mar 7, 2025): - Please open an issue in this repo instead, because we need more information regarding the tool's version. - https://github.com/langgenius/dify-official-plugins/
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#8119