[Bug]: <DescribeCollectionException: (code=1, message=can't find collection[database=default][collection=Vector_index_d08e3acd_d0c6_40c0_8047_2ade9fcc95ac_Node])>

[xujh-0522]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

- Milvus version:
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

当我通过dify知识库上传文件时报错 [Bug]: <DescribeCollectionException: (code=1, message=can't find collection[database=default][collection=Vector_index_d08e3acd_d0c6_40c0_8047_2ade9fcc95ac_Node])>

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[xiaofan-luan]

Is there an existing issue for this?

• [x] I have searched the existing issues

Environment

- Milvus version:
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

当我通过dify知识库上传文件时报错 [Bug]: <DescribeCollectionException: (code=1, message=can't find collection[database=default][collection=Vector_index_d08e3acd_d0c6_40c0_8047_2ade9fcc95ac_Node])>

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

is there a log for your milvus. or can you reproduce this issue or tell us how to reproduce this issue?

[yanliang567]

@xujh-0522 also please share the milvus and sdk versions. In case you don't know how to export the milvus logs: please refer this doc to export the whole Milvus logs. For Milvus installed with docker-compose, you can use docker-compose logs > milvus.log to export the logs. /assign @xujh-0522 /unassign

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.