langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Fine-tuned Cohere Rerank model is not shown in Model Providers list #511

New Issue
Closed
opened 2026-02-16 10:19:37 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 10:19:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @MasanoriOyabu on GitHub (Aug 4, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.7.1

Cloud or Self Hosted

Cloud

Steps to reproduce

  1. Finished a Cohere Rerank fine-tune job
  2. Dify ▸ Settings ▸ Model Providers ▸ Cohere ▸ “＋ Add model”
    • Model Type → Rerank
    • Model Name + API Key + API Base set, Save
    • Toast “Connection test success” appears
  3. Model-providers list stays 29 entries (should be 30) – no new row
  4. Knowledge ▸ Retrieval Settings drop-down also does not list the new model
  5. Retrieval Test & Logs never show the custom model ID

✔️ Expected Behavior

  • After saving, the Cohere provider list should become 30 items
    and show the newly added Rerank model (toggle ON).
  • The model should appear in Retrieval Settings ▸ Rerank Model drop-down
    so it can be selected for datasets.

❌ Actual Behavior

  • “Success” toast is shown, but provider count stays 29
    and no row is rendered for the custom model ID.
  • Therefore the model cannot be selected anywhere, and
    logs keep calling the default Cohere Rerank model.
Originally created by @MasanoriOyabu on GitHub (Aug 4, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.7.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce 1. Finished a Cohere **Rerank** fine-tune job 2. Dify ▸ **Settings ▸ Model Providers ▸ Cohere ▸ “＋ Add model”** * Model Type → **Rerank** * Model Name + API Key + API Base set, **Save** * Toast *“Connection test success”* appears 3. Model-providers list stays **29** entries (should be 30) – no new row 4. **Knowledge ▸ Retrieval Settings** drop-down also does **not** list the new model 5. Retrieval Test & Logs never show the custom model ID ### ✔️ Expected Behavior * After saving, the Cohere provider list should become **30** items and show the newly added Rerank model (toggle ON). * The model should appear in **Retrieval Settings ▸ Rerank Model** drop-down so it can be selected for datasets. ### ❌ Actual Behavior * “Success” toast is shown, but provider count stays **29** and no row is rendered for the custom model ID. * Therefore the model cannot be selected anywhere, and logs keep calling the default Cohere Rerank model.
yindo closed this issue 2026-02-16 10:19:37 -05:00
yindo commented 2026-02-16 10:19:37 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 4, 2025):

Hi @MasanoriOyabu! I'm Dosu and I’m helping the dify team.

The most common reason a fine-tuned Cohere Rerank model doesn't appear in the Model Providers list or Retrieval Settings is that it isn't fully registered or marked as active/enabled in the backend. The "Connection test success" toast only confirms the endpoint is reachable, not that the model is saved and visible in the UI.

Dify lists models that are present, valid, and enabled (status ACTIVE) in its backend tables. If a model is missing, it's usually because it wasn't inserted correctly, is not marked as valid, or is not enabled. Models with status DISABLED, NO_CONFIGURE, NO_PERMISSION, or QUOTA_EXCEEDED, or those marked deprecated, won't show up or be selectable in the UI or API. There is no code logic that specifically filters out Cohere Rerank or fine-tuned models—listing is dynamic and based on backend state (source).

Recent Dify versions added stricter validation for model providers and rerank models, so incomplete configuration or missing credentials can prevent models from appearing. If you’re on Dify Cloud and the model still doesn’t show up after a successful connection test, check for any error messages in your browser console or server logs when you try to add the model. If possible, verify with your admin or support that the model is present and enabled in the backend (ProviderModel and ProviderModelSetting tables) and not marked as deprecated or disabled (source).

If everything looks correct but the model still doesn’t appear, there may be a backend registration issue or a bug with how fine-tuned rerank models are handled. In that case, collect any relevant logs or error messages and share them with support for further troubleshooting.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 4, 2025): <!-- Greeting --> Hi @MasanoriOyabu! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The most common reason a fine-tuned Cohere Rerank model doesn't appear in the Model Providers list or Retrieval Settings is that it isn't fully registered or marked as active/enabled in the backend. The "Connection test success" toast only confirms the endpoint is reachable, not that the model is saved and visible in the UI. Dify lists models that are present, valid, and enabled (status ACTIVE) in its backend tables. If a model is missing, it's usually because it wasn't inserted correctly, is not marked as valid, or is not enabled. Models with status DISABLED, NO_CONFIGURE, NO_PERMISSION, or QUOTA_EXCEEDED, or those marked deprecated, won't show up or be selectable in the UI or API. There is no code logic that specifically filters out Cohere Rerank or fine-tuned models—listing is dynamic and based on backend state ([source](https://github.com/langgenius/dify/blob/8041808b53610275283bf6cbc0a44f8a163da254/api/core/entities/provider_configuration.py)). Recent Dify versions added stricter validation for model providers and rerank models, so incomplete configuration or missing credentials can prevent models from appearing. If you’re on Dify Cloud and the model still doesn’t show up after a successful connection test, check for any error messages in your browser console or server logs when you try to add the model. If possible, verify with your admin or support that the model is present and enabled in the backend (ProviderModel and ProviderModelSetting tables) and not marked as deprecated or disabled ([source](https://github.com/langgenius/dify/issues/22199)). If everything looks correct but the model still doesn’t appear, there may be a backend registration issue or a bug with how fine-tuned rerank models are handled. In that case, collect any relevant logs or error messages and share them with support for further troubleshooting. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/344672d6-4672-4344-a08f-c899cc52342e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/344672d6-4672-4344-a08f-c899cc52342e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/344672d6-4672-4344-a08f-c899cc52342e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/344672d6-4672-4344-a08f-c899cc52342e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/344672d6-4672-4344-a08f-c899cc52342e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/344672d6-4672-4344-a08f-c899cc52342e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/344672d6-4672-4344-a08f-c899cc52342e?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/23356)
yindo commented 2026-02-16 10:19:37 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 4, 2025):

Not sure if it's related to cache, but have you tried to refresh the page to see if it works?

@crazywoola commented on GitHub (Aug 4, 2025): Not sure if it's related to cache, but have you tried to refresh the page to see if it works?
yindo commented 2026-02-16 10:19:37 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 31, 2025):

Hi, @MasanoriOyabu. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that after fine-tuning and adding a Cohere Rerank model in Dify v1.7.1 cloud, the model does not appear in the Model Providers list or Retrieval Settings dropdown.
  • The connection test for the model endpoint succeeds, but the model is not usable in the UI.
  • I explained that a successful connection test only confirms endpoint reachability; the model must be fully registered, valid, and active in the backend to show up.
  • I suggested checking backend status, browser console, and server logs for errors, and refreshing the page to rule out caching issues.
  • The issue remains unresolved with no further updates.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 31, 2025): Hi, @MasanoriOyabu. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that after fine-tuning and adding a Cohere Rerank model in Dify v1.7.1 cloud, the model does not appear in the Model Providers list or Retrieval Settings dropdown. - The connection test for the model endpoint succeeds, but the model is not usable in the UI. - I explained that a successful connection test only confirms endpoint reachability; the model must be fully registered, valid, and active in the backend to show up. - I suggested checking backend status, browser console, and server logs for errors, and refreshing the page to rule out caching issues. - The issue remains unresolved with no further updates. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 5 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#511
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?