mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
langgenius/tongyi The installation was successful, but it is not included in the plugin #396
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dingdingkaifa on GitHub (Jun 24, 2025).
Self Checks
Dify version
1.4.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
All other plugins in the marketplace can be successfully installed, except for langgenius/tongyi which shows successful installation but not successful. Moreover, in the task, it consistently shows that the installation is in progress. Even after reinstalling, it still prompts for successful installation, but in reality, it is not successful.
Multiple versions have been installed, and both local upload and market installation have been unsuccessful.
The following is about langgenius/tongyi logs
✔️ Expected Behavior
I suspect there is a historical installation record that caused the consistent failure. Can you clearly record and reinstall it.
❌ Actual Behavior
Continuous installation failures
@dingdingkaifa commented on GitHub (Jun 24, 2025):
@dosubot[bot] commented on GitHub (Jun 24, 2025):
Hi @dingdingkaifa! I'm Dosu and I’m helping the dify team.
Your logs show dependency installation failures and possible network or resource issues during the plugin install. Dify tracks plugin installation tasks in the backend, and failed or stuck tasks can block reinstallation. The backend provides a way to clear all plugin installation task records for your tenant, which can help reset the state and allow a clean install. This can be done via the admin/console dashboard or API, using the endpoint that deletes all plugin installation task items for your tenant. See the relevant backend logic here: plugin.py and plugin_service.py.
After clearing the installation tasks, try reinstalling the plugin. If dependency installation still fails, check your Docker resource limits (CPU/memory), network stability, and consider cleaning the pip cache inside the plugin environment. If you need to automate the reset, the endpoint for deleting all install tasks is exposed in the backend and can be triggered for your tenant.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

@hjlarry commented on GitHub (Jul 2, 2025):
change the environment variable
PYTHON_ENV_INIT_TIMEOUTand then re-install the plugin@dosubot[bot] commented on GitHub (Aug 20, 2025):
Hi, @dingdingkaifa. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!