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
The error you're encountering with the AIPPT tool in Dify version 0.15.3 might be related to known issues or system errors. One known issue in this version is the error 'There is no item named NULL in the archive' when processing certain DOCX files. This is due to compatibility issues between the Document Extractor tool and certain DOCX file structures. A workaround is to convert the problematic DOCX files to a standard format before processing them through the tool [1].
Additionally, common causes of system errors in the AIPPT tool include issues like app not found, provider not initialized, quota exceeded, unsupported models, and more [2][3][4][5]. It might be helpful to check if any of these issues apply to your situation.
The error you're encountering with the AIPPT tool in Dify version 0.15.3 might be related to known issues or system errors. One known issue in this version is the error 'There is no item named NULL in the archive' when processing certain DOCX files. This is due to compatibility issues between the Document Extractor tool and certain DOCX file structures. A workaround is to convert the problematic DOCX files to a standard format before processing them through the tool [1].
Additionally, common causes of system errors in the AIPPT tool include issues like app not found, provider not initialized, quota exceeded, unsupported models, and more [2][3][4][5]. It might be helpful to check if any of these issues apply to your situation.
AIPPT back office balance is sufficient
If you do not enter the outline, only the title can be generated normally. Once you enter the outline, an error will occur.
And I am directly running AIPPT this step
Self Checks
Dify version
0.15.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: