From 582340a184d79324bfea1a4a53a2c97ec5a5df54 Mon Sep 17 00:00:00 2001
From: writinwaters <93570324+writinwaters@users.noreply.github.com>
Date: Tue, 16 Apr 2024 16:55:44 +0800
Subject: [PATCH] Added FAQ why document parsing gets stuck (#385)

### What problem does this PR solve?


### Type of change


- [x] Documentation Update
---
 docs/faq.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/faq.md b/docs/faq.md
index 959fcf573..49eee7e62 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -90,6 +90,17 @@ Ignore this warning and continue. All system warnings can be ignored.
 
 Parsing requests have to wait in queue due to limited server resources. We are currently enhancing our algorithms and increasing computing power.
 
+### Why does my document parsing stall at under one percent?
+
+If your RAGFlow is deployed *locally*, try the following: 
+
+1. Check the log of your RAGFlow server to see if it is running properly:
+```bash
+docker logs -f ragflow-server
+```
+2. Check if the **tast_executor.py** process exist.
+3. Check if your RAGFlow server can access hf-mirror.com or huggingface.com.
+
 ### How to handle `Index failure`?
 
 An index failure usually indicates an unavailable Elasticsearch service.