Add a new `/documents/reprocess_failed` API endpoint and corresponding UI button to retry processing of failed and pending documents. This addresses a common recovery scenario when document processing fails due to server crashes, network errors, or LLM service outages. Backend changes: - Add ReprocessResponse model with status, message, and track_id fields - Add POST /documents/reprocess_failed endpoint that triggers background reprocessing of FAILED, PENDING, and interrupted PROCESSING documents - Reuses existing apipeline_process_enqueue_documents for consistency - Includes comprehensive docstring and logging for observability Frontend changes: - Add TypeScript types and API function for the new endpoint - Add retry handler with intelligent polling (fast refresh → normal) - Add "Retry Failed" button in Documents page toolbar - Button disabled when pipeline is busy to prevent duplicate operations - Complete i18n support (English and Chinese translations) This feature provides a convenient way to recover from processing failures without requiring a full filesystem rescan. |
||
|---|---|---|
| .. | ||
| api | ||
| kg | ||
| llm | ||
| tools | ||
| __init__.py | ||
| base.py | ||
| constants.py | ||
| exceptions.py | ||
| lightrag.py | ||
| namespace.py | ||
| operate.py | ||
| prompt.py | ||
| rerank.py | ||
| types.py | ||
| utils.py | ||
| utils_graph.py | ||