After upgrading to v1.8.0, Ollama model settings cannot be edited

[gakugaku]

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 Dify issues & Dify Official Plugins, 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

1.8.0

Plugin version

0.0.7

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. Upgrade Dify from v1.7.2 to v1.8.0 (environment contains Ollama models).
2. In Model Providers → Add Model, choose provider Ollama and select an existing credential (e.g. API_KEY1).
3. The following error occurs:
   • Credential with id xxxxx not found.
   • The Add model credential form is missing fields: Base URL, Model context size, and Upper bound for max tokens.
   • Because of the missing fields, the model cannot be saved.

Note

• Ollama models created in v1.7.2 can still run successfully in v1.8.0, but cannot be edited.
• Newly created Ollama models in v1.8.0 can be edited without any issue.

✔️ Error log

No related logs were recorded during the error in the following containers

• docker container logs aitool_develop-dify-api-1
• docker container logs aitool_develop-dify-web-1
• docker container logs aitool_develop-dify-db-1

[dosubot]

This issue is caused by breaking changes in Dify v1.8.0's credential management. The upgrade introduced new tables (provider_credentials, provider_model_credentials) and migration scripts that move credential data and assign new credential IDs. If the migration was incomplete or references are broken, migrated Ollama models may reference credential IDs that no longer exist, resulting in the "Credential with id xxxxx not found" error and missing form fields like Base URL, context size, and max tokens. Newly created models work because their credentials are correctly registered in the new tables.

To fix this, you’ll need to manually inspect your database and ensure that each migrated Ollama model’s credential_id in the provider_models table matches a valid entry in provider_model_credentials. If not, you can create a new credential entry and update the reference. Also, make sure all required fields are present in the credential record. This will restore the edit functionality for migrated models. For details on the migration scripts and schema changes, see PR #24451 and PR #24545.

If you need a step-by-step SQL outline for this fix, let me know your database type and I can help draft it.

To reply, just mention @dosu.

---

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