mirror of
https://github.com/infiniflow/ragflow.git
synced 2026-07-06 19:38:36 +08:00
68
docs/faq.mdx
68
docs/faq.mdx
@@ -261,6 +261,74 @@ Ignore this warning and continue. All system warnings can be ignored.
|
||||
|
||||
---
|
||||
|
||||
### `xxx tasks are ahead in the queue`
|
||||
|
||||
### For RAGFlow versions earlier than v0.26.0
|
||||
|
||||
1. Clear the Redis task queue:
|
||||
|
||||
```bash
|
||||
$ docker exec -it ragflow-redis /bin/bash
|
||||
# In container
|
||||
$ redis-cli -a infini_rag_flow
|
||||
# In redis-cli
|
||||
select 1
|
||||
XGROUP DESTROY rag_flow_svr_queue rag_flow_svr_task_broker
|
||||
XGROUP CREATE rag_flow_svr_queue rag_flow_svr_task_broker $ MKSTREAM
|
||||
# When CREATE raises and error:
|
||||
FLUSHDB
|
||||
```
|
||||
|
||||
2. If the parser remains stuck at 0%, restart the RAGFlow containers using one of the following methods:
|
||||
|
||||
```bash
|
||||
# Option 1: Restart specific container
|
||||
docekr restart docker-redis-1 docker-ragflow-cpu-1
|
||||
|
||||
# Option 2: Recreate containers via Docker Compose
|
||||
docker compose -f docker/docker-compose.yml down
|
||||
docker compose -f docker/docker-compose.yml up -d
|
||||
|
||||
# Option 3: Reset all Docker containers
|
||||
# WARNING: Run this ONLY if your environment contains no other non-RAGFlow containers.
|
||||
docker stop $(docker ps -aq)
|
||||
docker rm $(docker ps -aq)
|
||||
```
|
||||
|
||||
### For RAGFlow v0.26.0 and later
|
||||
|
||||
1. Clear the Redis task queue:
|
||||
|
||||
```bash
|
||||
$ docker exec -it ragflow-redis /bin/bash
|
||||
# In container
|
||||
$ redis-cli -a infini_rag_flow
|
||||
# In redis-cli
|
||||
select 1
|
||||
XGROUP DESTROY te.0.common_queue te.0.common_task_broker
|
||||
XGROUP CREATE te.0.common_queue te.0.common_task_broker $ MKSTREAM
|
||||
# When CREATE raises and error:
|
||||
FLUSHDB
|
||||
```
|
||||
|
||||
2. If the parser remains stuck at 0%, restart the RAGFlow containers using one of the following methods:
|
||||
|
||||
```bash
|
||||
# Option 1: Restart specific container
|
||||
docekr restart docker-redis-1 docker-ragflow-cpu-1
|
||||
|
||||
# Option 2: Recreate containers via Docker Compose
|
||||
docker compose -f docker/docker-compose.yml down
|
||||
docker compose -f docker/docker-compose.yml up -d
|
||||
|
||||
# Option 3: Reset all Docker containers
|
||||
# WARNING: Run this ONLY if your environment contains no other non-RAGFlow containers.
|
||||
docker stop $(docker ps -aq)
|
||||
docker rm $(docker ps -aq)
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Why does my document parsing stall at under one percent?
|
||||
|
||||

|
||||
|
||||
@@ -46,7 +46,7 @@ Released on June 29, 2026.
|
||||
- Dataflow
|
||||
- Restores the dataflow rerun endpoint and ensures the ingestion response includes the DSL payload to reliably render the timeline and parser views. [#16292](https://github.com/infiniflow/ragflow/pull/16292)
|
||||
- Restores dataflow parser defaults and returns the actual SSE payload, ensuring pipeline runs correctly surface message IDs and log updates. [#16290](https://github.com/infiniflow/ragflow/pull/16290)
|
||||
- LLM: Failed to use the new `gemini-3.5-flash` model via the Google Cloud (Vertex AI) provider using `eu` or `us` region endpoint. This is resolved by explicitly multi-region routing requests to the required `aiplatform.<region>.rep.googleapis.com` domains instead of synthesized `<region>-aiplatform.googleapis.com` hosts. [#15990](https://github.com/infiniflow/ragflow/pull/15990)
|
||||
- LLM: Failed to use the new `gemini-3.5-flash` model via the Google Cloud (Vertex AI) provider using `eu` or `us` region endpoint. This is resolved by explicitly routing multi-region requests to the required `aiplatform.<region>.rep.googleapis.com` domains instead of the synthesized `<region>-aiplatform.googleapis.com` hosts. [#15990](https://github.com/infiniflow/ragflow/pull/15990)
|
||||
- UI/UX: The metadata add modal sent empty values to the backend. [#15229](https://github.com/infiniflow/ragflow/pull/15229)
|
||||
|
||||
## v0.26.1
|
||||
|
||||
Reference in New Issue
Block a user