[Question]: Bypassing/purging problematic tasks ?

[Randname666]

Describe your problem

A problematic task (how it's generated is unknown) is clogging up all other new tasks dispatched including non-PDF ones. The problematic task is nowhere to be found to be canceled in the WebUI. Currently the backend is giving out such errors constantly:

ragflow-server  | [WARNING] Load term.freq FAIL!
ragflow-server  | Traceback (most recent call last):
ragflow-server  |   File "/ragflow/rag/svr/task_executor.py", line 375, in <module>
ragflow-server  |     main()
ragflow-server  |   File "/ragflow/rag/svr/task_executor.py", line 294, in main
ragflow-server  |     rows = collect()
ragflow-server  |   File "/ragflow/rag/svr/task_executor.py", line 117, in collect
ragflow-server  |     assert tasks, "{} empty task!".format(msg["id"])
ragflow-server  | AssertionError: 2077fa703a6311efbc6f0242ac120006 empty task!
ragflow-mysql   | 2024-07-05T01:08:14.129120Z 28 [Note] Aborted connection 28 to db: 'rag_flow' user: 'root' host: '172.19.0.6' (Got an error reading communication packets)

docker compose down then docker compose up doesn't resolve the issue.

Is there a way to manually remove this problematic task? Additionally, is there a mechanism for task purging/canceling on error internally ?