The file upload to the knowledge base is always stuck in the queue. #8327

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

Originally created by @roMummy on GitHub (Feb 17, 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

  1. selected a file to upload to the knowledge base, but I deleted it while it was being processed.
  2. uploaded a new file to the knowledge base successfully, but it keeps showing as "in queue."
  3. the log by docker-worker-1:
2025-02-17 15:25:29 2025-02-17 07:25:29.568 ERROR [ThreadPoolExecutor-6_4] [cached_embedding.py:98] - Failed to embed documents: %s
2025-02-17 15:25:29 Traceback (most recent call last):
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2118, in _exec_insertmany_context
2025-02-17 15:25:29     dialect.do_execute(
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 941, in do_execute
2025-02-17 15:25:29     cursor.execute(statement, parameters)
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/psycogreen/gevent.py", line 32, in gevent_wait_callback
2025-02-17 15:25:29     state = conn.poll()
2025-02-17 15:25:29             ^^^^^^^^^^^
2025-02-17 15:25:29 psycopg2.OperationalError: FATAL:  terminating connection due to administrator command
2025-02-17 15:25:29 server closed the connection unexpectedly
2025-02-17 15:25:29     This probably means the server terminated abnormally
2025-02-17 15:25:29     before or while processing the request.
2025-02-17 15:25:29 
2025-02-17 15:25:29 
2025-02-17 15:25:29 The above exception was the direct cause of the following exception:
2025-02-17 15:25:29 
2025-02-17 15:25:29 Traceback (most recent call last):
2025-02-17 15:25:29   File "/app/api/core/rag/embedding/cached_embedding.py", line 93, in embed_documents
2025-02-17 15:25:29     db.session.commit()
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/scoping.py", line 597, in commit
2025-02-17 15:25:29     return self._proxied.commit()
2025-02-17 15:25:29            ^^^^^^^^^^^^^^^^^^^^^^
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 2028, in commit
2025-02-17 15:25:29     trans.commit(_to_root=True)
2025-02-17 15:25:29   File "<string>", line 2, in commit
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go
2025-02-17 15:25:29     ret_value = fn(self, *arg, **kw)
2025-02-17 15:25:29                 ^^^^^^^^^^^^^^^^^^^^
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 1313, in commit
2025-02-17 15:25:29     self._prepare_impl()
2025-02-17 15:25:29   File "<string>", line 2, in _prepare_impl
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go
2025-02-17 15:25:29     ret_value = fn(self, *arg, **kw)
2025-02-17 15:25:29                 ^^^^^^^^^^^^^^^^^^^^
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 1288, in _prepare_impl
2025-02-17 15:25:29     self.session.flush()
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 4352, in flush
2025-02-17 15:25:29     self._flush(objects)
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 4487, in _flush
2025-02-17 15:25:29     with util.safe_reraise():
2025-02-17 15:25:29          ^^^^^^^^^^^^^^^^^^^
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__
2025-02-17 15:25:29     raise exc_value.with_traceback(exc_tb)
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 4448, in _flush
2025-02-17 15:25:29     flush_context.execute()
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/unitofwork.py", line 466, in execute
2025-02-17 15:25:29     rec.execute(self)
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/unitofwork.py", line 642, in execute
2025-02-17 15:25:29     util.preloaded.orm_persistence.save_obj(
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/persistence.py", line 93, in save_obj
2025-02-17 15:25:29     _emit_insert_statements(
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/persistence.py", line 1143, in _emit_insert_statements
2025-02-17 15:25:29     result = connection.execute(
2025-02-17 15:25:29              ^^^^^^^^^^^^^^^^^^^
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1418, in execute
2025-02-17 15:25:29     return meth(
2025-02-17 15:25:29            ^^^^^
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/sql/elements.py", line 515, in _execute_on_connection
2025-02-17 15:25:29     return connection._execute_clauseelement(
2025-02-17 15:25:29            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1640, in _execute_clauseelement
2025-02-17 15:25:29     ret = self._execute_context(
2025-02-17 15:25:29           ^^^^^^^^^^^^^^^^^^^^^^
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1844, in _execute_context
2025-02-17 15:25:29     return self._exec_insertmany_context(dialect, context)
2025-02-17 15:25:29            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2126, in _exec_insertmany_context
2025-02-17 15:25:29     self._handle_dbapi_exception(
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2355, in _handle_dbapi_exception
2025-02-17 15:25:29     raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2118, in _exec_insertmany_context
2025-02-17 15:25:29     dialect.do_execute(
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 941, in do_execute
2025-02-17 15:25:29     cursor.execute(statement, parameters)
2025-02-17 15:25:29   File "/app/api/.venv/lib/python3.12/site-packages/psycogreen/gevent.py", line 32, in gevent_wait_callback
2025-02-17 15:25:29     state = conn.poll()
2025-02-17 15:25:29             ^^^^^^^^^^^
2025-02-17 15:25:29 sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) FATAL:  terminating connection due to administrator command
2025-02-17 15:25:29 server closed the connection unexpectedly
2025-02-17 15:25:29     This probably means the server terminated abnormally
2025-02-17 15:25:29     before or while processing the request.
2025-02-17 15:25:29 
2025-02-17 15:25:29 [SQL: INSERT INTO embeddings (model_name, hash, embedding, provider_name) VALUES (%(model_name)s, %(hash)s, %(embedding)s, %(provider_name)s) RETURNING embeddings.id, embeddings.created_at]
2025-02-17 15:25:29 [parameters: {'model_name': 'deepseek-r1:7b', 'hash': 'b81e8949dd65cdf455950d01c4a54f18d6d92a67b1f6b01cb2bae3d3fe1678ec', 'embedding': <psycopg2.extensions.Binary object at 0xffff6398a4f0>, 'provider_name': 'ollama'}]
2025-02-17 15:25:29 (Background on this error at: https://sqlalche.me/e/20/e3q8)
2025-02-17 15:26:18 2025-02-17 07:26:18.083 WARNING [ThreadPoolExecutor-6_9] [cached_embedding.py:72] - Normalized embedding is nan: [nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan...]

✔️ Expected Behavior

Successfully imported the file and created the knowledge base

Actual Behavior

It keeps showing as "in queue."

Originally created by @roMummy on GitHub (Feb 17, 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 1. selected a file to upload to the knowledge base, but I deleted it while it was being processed. 2. uploaded a new file to the knowledge base successfully, but it keeps showing as "in queue." 3. the log by `docker-worker-1`: ``` 2025-02-17 15:25:29 2025-02-17 07:25:29.568 ERROR [ThreadPoolExecutor-6_4] [cached_embedding.py:98] - Failed to embed documents: %s 2025-02-17 15:25:29 Traceback (most recent call last): 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2118, in _exec_insertmany_context 2025-02-17 15:25:29 dialect.do_execute( 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 941, in do_execute 2025-02-17 15:25:29 cursor.execute(statement, parameters) 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/psycogreen/gevent.py", line 32, in gevent_wait_callback 2025-02-17 15:25:29 state = conn.poll() 2025-02-17 15:25:29 ^^^^^^^^^^^ 2025-02-17 15:25:29 psycopg2.OperationalError: FATAL: terminating connection due to administrator command 2025-02-17 15:25:29 server closed the connection unexpectedly 2025-02-17 15:25:29 This probably means the server terminated abnormally 2025-02-17 15:25:29 before or while processing the request. 2025-02-17 15:25:29 2025-02-17 15:25:29 2025-02-17 15:25:29 The above exception was the direct cause of the following exception: 2025-02-17 15:25:29 2025-02-17 15:25:29 Traceback (most recent call last): 2025-02-17 15:25:29 File "/app/api/core/rag/embedding/cached_embedding.py", line 93, in embed_documents 2025-02-17 15:25:29 db.session.commit() 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/scoping.py", line 597, in commit 2025-02-17 15:25:29 return self._proxied.commit() 2025-02-17 15:25:29 ^^^^^^^^^^^^^^^^^^^^^^ 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 2028, in commit 2025-02-17 15:25:29 trans.commit(_to_root=True) 2025-02-17 15:25:29 File "<string>", line 2, in commit 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go 2025-02-17 15:25:29 ret_value = fn(self, *arg, **kw) 2025-02-17 15:25:29 ^^^^^^^^^^^^^^^^^^^^ 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 1313, in commit 2025-02-17 15:25:29 self._prepare_impl() 2025-02-17 15:25:29 File "<string>", line 2, in _prepare_impl 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go 2025-02-17 15:25:29 ret_value = fn(self, *arg, **kw) 2025-02-17 15:25:29 ^^^^^^^^^^^^^^^^^^^^ 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 1288, in _prepare_impl 2025-02-17 15:25:29 self.session.flush() 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 4352, in flush 2025-02-17 15:25:29 self._flush(objects) 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 4487, in _flush 2025-02-17 15:25:29 with util.safe_reraise(): 2025-02-17 15:25:29 ^^^^^^^^^^^^^^^^^^^ 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ 2025-02-17 15:25:29 raise exc_value.with_traceback(exc_tb) 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 4448, in _flush 2025-02-17 15:25:29 flush_context.execute() 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/unitofwork.py", line 466, in execute 2025-02-17 15:25:29 rec.execute(self) 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/unitofwork.py", line 642, in execute 2025-02-17 15:25:29 util.preloaded.orm_persistence.save_obj( 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/persistence.py", line 93, in save_obj 2025-02-17 15:25:29 _emit_insert_statements( 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/orm/persistence.py", line 1143, in _emit_insert_statements 2025-02-17 15:25:29 result = connection.execute( 2025-02-17 15:25:29 ^^^^^^^^^^^^^^^^^^^ 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1418, in execute 2025-02-17 15:25:29 return meth( 2025-02-17 15:25:29 ^^^^^ 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/sql/elements.py", line 515, in _execute_on_connection 2025-02-17 15:25:29 return connection._execute_clauseelement( 2025-02-17 15:25:29 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1640, in _execute_clauseelement 2025-02-17 15:25:29 ret = self._execute_context( 2025-02-17 15:25:29 ^^^^^^^^^^^^^^^^^^^^^^ 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1844, in _execute_context 2025-02-17 15:25:29 return self._exec_insertmany_context(dialect, context) 2025-02-17 15:25:29 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2126, in _exec_insertmany_context 2025-02-17 15:25:29 self._handle_dbapi_exception( 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2355, in _handle_dbapi_exception 2025-02-17 15:25:29 raise sqlalchemy_exception.with_traceback(exc_info[2]) from e 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2118, in _exec_insertmany_context 2025-02-17 15:25:29 dialect.do_execute( 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 941, in do_execute 2025-02-17 15:25:29 cursor.execute(statement, parameters) 2025-02-17 15:25:29 File "/app/api/.venv/lib/python3.12/site-packages/psycogreen/gevent.py", line 32, in gevent_wait_callback 2025-02-17 15:25:29 state = conn.poll() 2025-02-17 15:25:29 ^^^^^^^^^^^ 2025-02-17 15:25:29 sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) FATAL: terminating connection due to administrator command 2025-02-17 15:25:29 server closed the connection unexpectedly 2025-02-17 15:25:29 This probably means the server terminated abnormally 2025-02-17 15:25:29 before or while processing the request. 2025-02-17 15:25:29 2025-02-17 15:25:29 [SQL: INSERT INTO embeddings (model_name, hash, embedding, provider_name) VALUES (%(model_name)s, %(hash)s, %(embedding)s, %(provider_name)s) RETURNING embeddings.id, embeddings.created_at] 2025-02-17 15:25:29 [parameters: {'model_name': 'deepseek-r1:7b', 'hash': 'b81e8949dd65cdf455950d01c4a54f18d6d92a67b1f6b01cb2bae3d3fe1678ec', 'embedding': <psycopg2.extensions.Binary object at 0xffff6398a4f0>, 'provider_name': 'ollama'}] 2025-02-17 15:25:29 (Background on this error at: https://sqlalche.me/e/20/e3q8) 2025-02-17 15:26:18 2025-02-17 07:26:18.083 WARNING [ThreadPoolExecutor-6_9] [cached_embedding.py:72] - Normalized embedding is nan: [nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan...] ``` ### ✔️ Expected Behavior Successfully imported the file and created the knowledge base ### ❌ Actual Behavior It keeps showing as "in queue."
yindo added the 🐞 bug label 2026-02-21 18:25:06 -05:00
yindo closed this issue 2026-02-21 18:25:06 -05:00
Author
Owner

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

Hello, @roMummy! I'm here to assist you with bug fixes, answer your questions, and guide you to become a contributor. Let's tackle this issue together!

I found some similar discussions and issues related to the problem of files being stuck in the queue when uploading to the knowledge base in Dify:

  1. The status of the Knowledge Base keeps showing ‘Queuing’ after adding a document - This discussion is unsolved but suggests checking the rate limit for the Embedding model API key and ensuring the Celery worker service is running correctly.

  2. Help: Document stuck in "Queuing" status after upload in Dify local deployment (non-Docker environment) - This discussion is also unsolved and recommends ensuring that all necessary services are running and checking the logs for any specific error messages.

  3. Perpetual queue for uploading a document to the knowledge base - This open issue suggests checking the rate limit for the Embedding model API key, ensuring the Celery worker service is running, and verifying that all necessary services are up.

To address the psycopg2.OperationalError related to terminating connections, ensure that all middleware services, including PostgreSQL, are running correctly. You can set up the required middleware services using Docker Compose:

cd docker
cp middleware.env.example middleware.env
docker compose -f docker-compose.middleware.yaml up -d

Additionally, verify that there are no firewall rules blocking the necessary ports, and ensure that the Python environment is correctly configured with Python 3.12 and all dependencies [1].

To continue talking to Dosu, mention @dosu.


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

@dosubot[bot] commented on GitHub (Feb 17, 2025): <!-- Greeting --> Hello, @roMummy! I'm here to assist you with bug fixes, answer your questions, and guide you to become a contributor. Let's tackle this issue together! <!-- Answer --> I found some similar discussions and issues related to the problem of files being stuck in the queue when uploading to the knowledge base in Dify: 1. **[The status of the Knowledge Base keeps showing ‘Queuing’ after adding a document](https://github.com/langgenius/dify/discussions/13683)** - This discussion is unsolved but suggests checking the rate limit for the Embedding model API key and ensuring the Celery worker service is running correctly. 2. **[Help: Document stuck in "Queuing" status after upload in Dify local deployment (non-Docker environment)](https://github.com/langgenius/dify/discussions/13739)** - This discussion is also unsolved and recommends ensuring that all necessary services are running and checking the logs for any specific error messages. 3. **[Perpetual queue for uploading a document to the knowledge base](https://github.com/langgenius/dify/issues/11911)** - This open issue suggests checking the rate limit for the Embedding model API key, ensuring the Celery worker service is running, and verifying that all necessary services are up. To address the `psycopg2.OperationalError` related to terminating connections, ensure that all middleware services, including PostgreSQL, are running correctly. You can set up the required middleware services using Docker Compose: ```bash cd docker cp middleware.env.example middleware.env docker compose -f docker-compose.middleware.yaml up -d ``` Additionally, verify that there are no firewall rules blocking the necessary ports, and ensure that the Python environment is correctly configured with Python 3.12 and all dependencies <sup>[[1]](https://github.com/langgenius/dify/issues/13806)</sup>. <!-- 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/b683fbbe-c4df-4b5d-99d1-bab4281514eb?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b683fbbe-c4df-4b5d-99d1-bab4281514eb?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b683fbbe-c4df-4b5d-99d1-bab4281514eb?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b683fbbe-c4df-4b5d-99d1-bab4281514eb?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b683fbbe-c4df-4b5d-99d1-bab4281514eb?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b683fbbe-c4df-4b5d-99d1-bab4281514eb?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b683fbbe-c4df-4b5d-99d1-bab4281514eb?feedback_type=other)</sup>
Author
Owner

@crazywoola commented on GitHub (Feb 17, 2025):

deepseek-r1:7b This is not a embedding model.

@crazywoola commented on GitHub (Feb 17, 2025): `deepseek-r1:7b` This is not a embedding model.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#8327