langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

The API key check logic in Dify is outdated. #696

New Issue
Closed
opened 2026-02-16 10:20:13 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:20:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @yuchiho2008 on GitHub (Oct 9, 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

Version 1.9.1

Cloud or Self Hosted

Cloud

Steps to reproduce

  • The API key check logic in Dify is outdated.
  • It still calls llama3-8b-8192 instead of a currently supported model.

Steps to reproduce

  • Go to Settings → Models → Add API
  • Select Groq as provider
  • Enter API Key from GroqCloud
  • Save

✔️ Expected Behavior

✔️ Expected Behavior
The Groq API credentials should validate successfully, and the model should be available for use in the workspace.

❌ Actual Behavior

❌ Actual Behavior
Validation fails with:
{"error":{"message":"The model llama3-8b-8192 has been decommissioned and is no longer supported. Please refer to https://console.groq.com/docs/deprecations for a recommendation on which model to use instead.","type":"invalid_request_error","code":"model_decommissioned"}}

Originally created by @yuchiho2008 on GitHub (Oct 9, 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 Version 1.9.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce - The API key check logic in Dify is outdated. - It still calls llama3-8b-8192 instead of a currently supported model. Steps to reproduce - Go to Settings → Models → Add API - Select Groq as provider - Enter API Key from GroqCloud - Save ### ✔️ Expected Behavior ✔️ Expected Behavior The Groq API credentials should validate successfully, and the model should be available for use in the workspace. ### ❌ Actual Behavior ❌ Actual Behavior Validation fails with: {"error":{"message":"The model `llama3-8b-8192` has been decommissioned and is no longer supported. Please refer to https://console.groq.com/docs/deprecations for a recommendation on which model to use instead.","type":"invalid_request_error","code":"model_decommissioned"}}
yindo added the good first issuebug labels 2026-02-16 10:20:13 -05:00
yindo closed this issue 2026-02-16 10:20:13 -05:00
yindo commented 2026-02-16 10:20:13 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 9, 2025):

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

The API key validation logic in Dify v1.9.1 is outdated and still references the deprecated Groq model llama3-8b-8192, which causes credential validation to fail. Recent updates have been merged to the codebase that address this issue by supporting multiple model credentials and ensuring only active models are used for validation. These changes are reflected in pull requests #24451 and #25759, which update backend logic to prevent deprecated models from being used during API key checks.

To resolve this, Dify needs to reference a currently supported Groq model, such as llama-3.1-8b-instant, for validation. If you are using the cloud deployment and still encountering this issue, it may be due to the cloud instance not yet running the latest code with these fixes. Once the updates are live, you should be able to add Groq API keys and select supported models without encountering the decommissioned model error.

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 (Oct 9, 2025): <!-- Greeting --> Hi @yuchiho2008! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The API key validation logic in Dify v1.9.1 is outdated and still references the deprecated Groq model `llama3-8b-8192`, which causes credential validation to fail. Recent updates have been merged to the codebase that address this issue by supporting multiple model credentials and ensuring only active models are used for validation. These changes are reflected in pull requests [#24451](https://github.com/langgenius/dify/pull/24451) and [#25759](https://github.com/langgenius/dify/pull/25759), which update backend logic to prevent deprecated models from being used during API key checks. To resolve this, Dify needs to reference a currently supported Groq model, such as `llama-3.1-8b-instant`, for validation. If you are using the cloud deployment and still encountering this issue, it may be due to the cloud instance not yet running the latest code with these fixes. Once the updates are live, you should be able to add Groq API keys and select supported models without encountering the decommissioned model error. <!-- 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/325a257b-0aa7-4b14-ab95-61ea60fb3ab3?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/325a257b-0aa7-4b14-ab95-61ea60fb3ab3?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/325a257b-0aa7-4b14-ab95-61ea60fb3ab3?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/325a257b-0aa7-4b14-ab95-61ea60fb3ab3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/325a257b-0aa7-4b14-ab95-61ea60fb3ab3?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/325a257b-0aa7-4b14-ab95-61ea60fb3ab3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/325a257b-0aa7-4b14-ab95-61ea60fb3ab3?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/26679)
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 bug good first issue
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#696
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?