You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
In the current Dify knowledge base pipeline, there is no visible status information in the UI while documents are being processed. Users cannot see the current progress, how much has been completed, which documents have been processed, or what step the pipeline is currently in.
Additionally, during the processing phase, almost no error information is exposed. Users only become aware of issues when the pipeline eventually fails, at which point the feedback is still very limited.
There should be an extension or hook mechanism that allows developers to customize and expose pipeline status information, or at least a default implementation that provides basic progress indicators and intermediate error reporting.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
In the current Dify knowledge base pipeline, there is no visible status information in the UI while documents are being processed. Users cannot see the current progress, how much has been completed, which documents have been processed, or what step the pipeline is currently in.
Additionally, during the processing phase, almost no error information is exposed. Users only become aware of issues when the pipeline eventually fails, at which point the feedback is still very limited.
There should be an extension or hook mechanism that allows developers to customize and expose pipeline status information, or at least a default implementation that provides basic progress indicators and intermediate error reporting.
2. Additional context or comments
No response
Beta Was this translation helpful? Give feedback.
All reactions