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

Unable to add or modify deepseek's apikey ,Credential record not found. #621

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

Originally created by @Zhongren233 on GitHub (Sep 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.8.1

Cloud or Self Hosted

Cloud

Steps to reproduce

On Model Provider,I try to remove my old api key,it tell me Credential record not found.
And when I add new api key although successful, the newly added API key is not displayed

✔️ Expected Behavior

Normally add or delete api key

❌ Actual Behavior

No response

Originally created by @Zhongren233 on GitHub (Sep 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.8.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce On Model Provider,I try to remove my old api key,it tell me Credential record not found. And when I add new api key although successful, the newly added API key is not displayed ### ✔️ Expected Behavior Normally add or delete api key ### ❌ Actual Behavior _No response_
yindo added the bug label 2026-02-16 10:19:56 -05:00
yindo closed this issue 2026-02-16 10:19:56 -05:00
yindo commented 2026-02-16 10:19:56 -05:00
Author
Owner
Copy Link
Copy Source

@Zhongren233 commented on GitHub (Sep 4, 2025):

I don't know if this is related to my account, but I don't think I should disclose my account in the issue.

@Zhongren233 commented on GitHub (Sep 4, 2025): I don't know if this is related to my account, but I don't think I should disclose my account in the issue.
yindo commented 2026-02-16 10:19:56 -05:00
Author
Owner
Copy Link
Copy Source

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

What's the version of the provider?

@crazywoola commented on GitHub (Sep 4, 2025): What's the version of the provider?
yindo commented 2026-02-16 10:19:56 -05:00
Author
Owner
Copy Link
Copy Source

@Zhongren233 commented on GitHub (Sep 5, 2025):

What's the version of the provider?

deepseek 0.0.5
might i need update version?

@Zhongren233 commented on GitHub (Sep 5, 2025): > What's the version of the provider? deepseek 0.0.5 might i need update version?
yindo commented 2026-02-16 10:19:56 -05:00
Author
Owner
Copy Link
Copy Source

@Zhongren233 commented on GitHub (Sep 5, 2025):

when i update to 0.0.6 still have the same problem

@Zhongren233 commented on GitHub (Sep 5, 2025): when i update to 0.0.6 still have the same problem
yindo commented 2026-02-16 10:19:56 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 5, 2025):

I tried but I can not reproduce this.

@crazywoola commented on GitHub (Sep 5, 2025): I tried but I can not reproduce this.
yindo commented 2026-02-16 10:19:56 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 5, 2025):

Hi @Zhongren233! I'm Dosu and I’m helping the dify-official-plugins team.

This issue is likely caused by a mismatch or missing credential record in the backend, which can happen if the credential ID sent for deletion or update doesn't exist for your workspace and provider. This is often due to recent changes in how credentials are stored and referenced—Dify recently migrated to a new credential system using uuidv7 for IDs, and any incomplete migration or stale frontend state can trigger the "Credential record not found" error. The fact that new API keys aren't displayed after adding them suggests a UI/backend sync problem, where the frontend isn't properly refreshing or the backend isn't returning the updated credential list after changes. This isn't Deepseek-specific and can affect any provider using the new credential framework (source).

Recent major refactors to credential management (see PRs #24994, #24451, #24545) may have introduced or fixed related bugs. If you're on Dify Cloud, these changes should be live, but if the issue persists, it's likely due to a backend/frontend sync bug or a migration issue (source).

As a workaround, try refreshing the Model Provider page after adding or deleting a key to force a UI update. If the problem continues, it's possible the credential records for Deepseek (or other providers) are out of sync—this would need to be addressed by ensuring all migrations are complete and the backend is correctly returning updated credential lists. If you have access to logs, check for errors related to credential ID mismatches or missing records during these operations.

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Sep 5, 2025): <!-- Greeting --> Hi @Zhongren233! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. <!-- Answer --> This issue is likely caused by a mismatch or missing credential record in the backend, which can happen if the credential ID sent for deletion or update doesn't exist for your workspace and provider. This is often due to recent changes in how credentials are stored and referenced—Dify recently migrated to a new credential system using uuidv7 for IDs, and any incomplete migration or stale frontend state can trigger the "Credential record not found" error. The fact that new API keys aren't displayed after adding them suggests a UI/backend sync problem, where the frontend isn't properly refreshing or the backend isn't returning the updated credential list after changes. This isn't Deepseek-specific and can affect any provider using the new credential framework ([source](https://github.com/langgenius/dify/blob/cd95237ae4c61b6d90a9977957aed22a33a26b74/api/core/entities/provider_configuration.py)). Recent major refactors to credential management (see PRs #24994, #24451, #24545) may have introduced or fixed related bugs. If you're on Dify Cloud, these changes should be live, but if the issue persists, it's likely due to a backend/frontend sync bug or a migration issue ([source](https://github.com/langgenius/dify/pull/24994)). As a workaround, try refreshing the Model Provider page after adding or deleting a key to force a UI update. If the problem continues, it's possible the credential records for Deepseek (or other providers) are out of sync—this would need to be addressed by ensuring all migrations are complete and the backend is correctly returning updated credential lists. If you have access to logs, check for errors related to credential ID mismatches or missing records during these operations. <!-- 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/af6545d6-9058-4047-95a1-1797d5c9daf1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/af6545d6-9058-4047-95a1-1797d5c9daf1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/af6545d6-9058-4047-95a1-1797d5c9daf1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/af6545d6-9058-4047-95a1-1797d5c9daf1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/af6545d6-9058-4047-95a1-1797d5c9daf1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/af6545d6-9058-4047-95a1-1797d5c9daf1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/af6545d6-9058-4047-95a1-1797d5c9daf1?feedback_type=other)</sup>&nbsp;&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-official-plugins/issues/1666)
yindo commented 2026-02-16 10:19:56 -05:00
Author
Owner
Copy Link
Copy Source

@Zhongren233 commented on GitHub (Sep 5, 2025):

Do I need to provide anything related to my account to troubleshoot?

@Zhongren233 commented on GitHub (Sep 5, 2025): Do I need to provide anything related to my account to troubleshoot?
yindo commented 2026-02-16 10:19:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 21, 2025):

Hi, @Zhongren233. 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 being unable to delete old API keys in Dify 1.8.1 Cloud due to a "Credential record not found" error.
  • Newly added keys do not display properly in the interface.
  • The issue is linked to backend/frontend sync problems after migrating to a new credential system using uuidv7 IDs.
  • This affects all providers, including Deepseek, even after updating to version 0.0.6.
  • A suggested workaround is refreshing the Model Provider page and checking logs for credential ID mismatches.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here.
  • If I don’t hear back within 5 days, I will automatically close this issue.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 21, 2025): Hi, @Zhongren233. 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 being unable to delete old API keys in Dify 1.8.1 Cloud due to a "Credential record not found" error. - Newly added keys do not display properly in the interface. - The issue is linked to backend/frontend sync problems after migrating to a new credential system using uuidv7 IDs. - This affects all providers, including Deepseek, even after updating to version 0.0.6. - A suggested workaround is refreshing the Model Provider page and checking logs for credential ID mismatches. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here. - If I don’t hear back within 5 days, I will automatically close this issue. Thanks 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 bug
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#621
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?