Internal Server Error (500) in Dify Application #20071

Closed
opened 2026-02-21 20:05:43 -05:00 by yindo · 11 comments
Owner

Originally created by @yumilious on GitHub (Oct 31, 2025).

Originally assigned to: @crazywoola on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.10.0-rc1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Create a ChatFlow, and the aforementioned error will occur.

Image

✔️ Expected Behavior

I hope this problem and the pop-up can be avoided.

Actual Behavior

But it actually appears.

Originally created by @yumilious on GitHub (Oct 31, 2025). Originally assigned to: @crazywoola on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.10.0-rc1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Create a ChatFlow, and the aforementioned error will occur. <img width="2560" height="1392" alt="Image" src="https://github.com/user-attachments/assets/81fe1903-fabc-44e7-8d8e-17f4ebfba6f2" /> ### ✔️ Expected Behavior I hope this problem and the pop-up can be avoided. ### ❌ Actual Behavior But it actually appears.
yindo added the 🐞 bug label 2026-02-21 20:05:43 -05:00
yindo closed this issue 2026-02-21 20:05:43 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Oct 31, 2025):

The 500 Internal Server Error you’re seeing when creating a ChatFlow is most likely caused by a backend issue—such as a misconfiguration, missing database records, or a problem with dependencies in your Docker setup. This error is triggered by repeated GET requests to /api/workspaces/current/triggers, which relies on correct workspace configuration, database connectivity, and feature toggles in the backend. Similar issues have been traced to missing or mismatched tool installations, database connection problems, or incomplete migrations in self-hosted environments example.

Here’s what you should check:

  • Inspect the logs of your api container (docker-compose logs api) for detailed error messages or stack traces. These often reveal the failing workflow node, plugin, or model call reference.
  • Make sure your database is healthy and all migrations are up to date. Missing tables or out-of-sync migrations can cause 500 errors reference.
  • Verify that all required environment variables (like database, Redis, and model provider keys) are set correctly in your Docker setup reference.
  • If you’re using plugins or tools in your workflow, confirm that the plugin_id and tenant_id match the installed tool and tenant in your database. Reinstalling the tool can fix database inconsistencies reference.
  • Restarting the system sometimes resolves transient issues, but if the error persists, focus on the logs and configuration reference.

If you can share the specific error or stack trace from your backend logs, I can help pinpoint the root cause more precisely.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Oct 31, 2025): <!-- Answer --> The 500 Internal Server Error you’re seeing when creating a ChatFlow is most likely caused by a backend issue—such as a misconfiguration, missing database records, or a problem with dependencies in your Docker setup. This error is triggered by repeated GET requests to `/api/workspaces/current/triggers`, which relies on correct workspace configuration, database connectivity, and feature toggles in the backend. Similar issues have been traced to missing or mismatched tool installations, database connection problems, or incomplete migrations in self-hosted environments [example](https://github.com/langgenius/dify/issues/16014). Here’s what you should check: - Inspect the logs of your `api` container (`docker-compose logs api`) for detailed error messages or stack traces. These often reveal the failing workflow node, plugin, or model call [reference](https://github.com/langgenius/dify/issues/14599). - Make sure your database is healthy and all migrations are up to date. Missing tables or out-of-sync migrations can cause 500 errors [reference](https://github.com/langgenius/dify/issues/26560). - Verify that all required environment variables (like database, Redis, and model provider keys) are set correctly in your Docker setup [reference](https://github.com/langgenius/dify-docs/issues/397#issuecomment-3191088755). - If you’re using plugins or tools in your workflow, confirm that the `plugin_id` and `tenant_id` match the installed tool and tenant in your database. Reinstalling the tool can fix database inconsistencies [reference](https://github.com/langgenius/dify/issues/16014). - Restarting the system sometimes resolves transient issues, but if the error persists, focus on the logs and configuration [reference](https://github.com/langgenius/dify/issues/14599). If you can share the specific error or stack trace from your backend logs, I can help pinpoint the root cause more precisely. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/ee3cfd0e-0898-4de8-85df-a35e287a037b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ee3cfd0e-0898-4de8-85df-a35e287a037b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ee3cfd0e-0898-4de8-85df-a35e287a037b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ee3cfd0e-0898-4de8-85df-a35e287a037b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ee3cfd0e-0898-4de8-85df-a35e287a037b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ee3cfd0e-0898-4de8-85df-a35e287a037b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ee3cfd0e-0898-4de8-85df-a35e287a037b?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27713)
Author
Owner

@hjlarry commented on GitHub (Nov 1, 2025):

Could you provide the logs for the API container?

@hjlarry commented on GitHub (Nov 1, 2025): Could you provide the logs for the API container?
Author
Owner

@yumilious commented on GitHub (Nov 1, 2025):

2025-11-01 08:29:25.092 ERROR [Dummy-24] [base.py:209] - Failed to request plugin daemon, status: 404, url: plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers

Traceback (most recent call last):

  File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response

    response.raise_for_status()

  File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status

    raise HTTPStatusError(message, request=request, response=self)

httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers?page=1&page_size=256'

For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404)

2025-11-01 08:29:25.092 ERROR [Dummy-24] [app.py:875] - Exception on /console/api/workspaces/current/triggers [GET]

Traceback (most recent call last):

  File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 917, in full_dispatch_request

    rv = self.dispatch_request()

         ^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 902, in dispatch_request

    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/.venv/lib/python3.12/site-packages/flask_restx/api.py", line 404, in wrapper

    resp = resource(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/.venv/lib/python3.12/site-packages/flask/views.py", line 110, in view

    return current_app.ensure_sync(self.dispatch_request)(**kwargs)  # type: ignore[no-any-return]

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/.venv/lib/python3.12/site-packages/flask_restx/resource.py", line 41, in dispatch_request

    resp = meth(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/controllers/console/wraps.py", line 219, in decorated

    return view(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/libs/login.py", line 80, in decorated_view

    return current_app.ensure_sync(func)(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/controllers/console/wraps.py", line 36, in decorated

    return view(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/controllers/console/workspace/trigger_providers.py", line 50, in get

    return jsonable_encoder(TriggerProviderService.list_trigger_providers(user.current_tenant_id))

                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/services/trigger/trigger_provider_service.py", line 61, in list_trigger_providers

    return [provider.to_api_entity() for provider in TriggerManager.list_all_trigger_providers(tenant_id)]

                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/trigger/trigger_manager.py", line 135, in list_all_trigger_providers

    return cls.list_plugin_trigger_providers(tenant_id)

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/trigger/trigger_manager.py", line 57, in list_plugin_trigger_providers

    provider_entities = manager.fetch_trigger_providers(tenant_id)

                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/plugin/impl/trigger.py", line 35, in fetch_trigger_providers

    response: list[PluginTriggerProviderEntity] = self._request_with_plugin_daemon_response(

                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/plugin/impl/base.py", line 210, in _request_with_plugin_daemon_response

    raise e

  File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response

    response.raise_for_status()

  File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status

    raise HTTPStatusError(message, request=request, response=self)

httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers?page=1&page_size=256'

For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404)

2025-11-01 08:29:25.092 ERROR [Dummy-24] [app.py:875] - Exception on /console/api/workspaces/current/triggers [GET]

Traceback (most recent call last):
@yumilious commented on GitHub (Nov 1, 2025): ``` 2025-11-01 08:29:25.092 ERROR [Dummy-24] [base.py:209] - Failed to request plugin daemon, status: 404, url: plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers Traceback (most recent call last): File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response response.raise_for_status() File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status raise HTTPStatusError(message, request=request, response=self) httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers?page=1&page_size=256' For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404) 2025-11-01 08:29:25.092 ERROR [Dummy-24] [app.py:875] - Exception on /console/api/workspaces/current/triggers [GET] Traceback (most recent call last): File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 917, in full_dispatch_request rv = self.dispatch_request() ^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 902, in dispatch_request return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/flask_restx/api.py", line 404, in wrapper resp = resource(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/flask/views.py", line 110, in view return current_app.ensure_sync(self.dispatch_request)(**kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/.venv/lib/python3.12/site-packages/flask_restx/resource.py", line 41, in dispatch_request resp = meth(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/app/api/controllers/console/wraps.py", line 219, in decorated return view(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/app/api/libs/login.py", line 80, in decorated_view return current_app.ensure_sync(func)(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/controllers/console/wraps.py", line 36, in decorated return view(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/app/api/controllers/console/workspace/trigger_providers.py", line 50, in get return jsonable_encoder(TriggerProviderService.list_trigger_providers(user.current_tenant_id)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/services/trigger/trigger_provider_service.py", line 61, in list_trigger_providers return [provider.to_api_entity() for provider in TriggerManager.list_all_trigger_providers(tenant_id)] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/trigger/trigger_manager.py", line 135, in list_all_trigger_providers return cls.list_plugin_trigger_providers(tenant_id) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/trigger/trigger_manager.py", line 57, in list_plugin_trigger_providers provider_entities = manager.fetch_trigger_providers(tenant_id) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/plugin/impl/trigger.py", line 35, in fetch_trigger_providers response: list[PluginTriggerProviderEntity] = self._request_with_plugin_daemon_response( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/plugin/impl/base.py", line 210, in _request_with_plugin_daemon_response raise e File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response response.raise_for_status() File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status raise HTTPStatusError(message, request=request, response=self) httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers?page=1&page_size=256' For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404) 2025-11-01 08:29:25.092 ERROR [Dummy-24] [app.py:875] - Exception on /console/api/workspaces/current/triggers [GET] Traceback (most recent call last): ```
Author
Owner

@crazywoola commented on GitHub (Nov 3, 2025):

@dosu

2025-11-01 08:29:25.092 ERROR [Dummy-24] [base.py:209] - Failed to request plugin daemon, status: 404, url: plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers

Traceback (most recent call last):

  File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response

    response.raise_for_status()

  File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status

    raise HTTPStatusError(message, request=request, response=self)

httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers?page=1&page_size=256'

For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404)

2025-11-01 08:29:25.092 ERROR [Dummy-24] [app.py:875] - Exception on /console/api/workspaces/current/triggers [GET]

Traceback (most recent call last):

  File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 917, in full_dispatch_request

    rv = self.dispatch_request()

         ^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 902, in dispatch_request

    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/.venv/lib/python3.12/site-packages/flask_restx/api.py", line 404, in wrapper

    resp = resource(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/.venv/lib/python3.12/site-packages/flask/views.py", line 110, in view

    return current_app.ensure_sync(self.dispatch_request)(**kwargs)  # type: ignore[no-any-return]

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/.venv/lib/python3.12/site-packages/flask_restx/resource.py", line 41, in dispatch_request

    resp = meth(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/controllers/console/wraps.py", line 219, in decorated

    return view(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/libs/login.py", line 80, in decorated_view

    return current_app.ensure_sync(func)(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/controllers/console/wraps.py", line 36, in decorated

    return view(*args, **kwargs)

           ^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/controllers/console/workspace/trigger_providers.py", line 50, in get

    return jsonable_encoder(TriggerProviderService.list_trigger_providers(user.current_tenant_id))

                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/services/trigger/trigger_provider_service.py", line 61, in list_trigger_providers

    return [provider.to_api_entity() for provider in TriggerManager.list_all_trigger_providers(tenant_id)]

                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/trigger/trigger_manager.py", line 135, in list_all_trigger_providers

    return cls.list_plugin_trigger_providers(tenant_id)

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/trigger/trigger_manager.py", line 57, in list_plugin_trigger_providers

    provider_entities = manager.fetch_trigger_providers(tenant_id)

                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/plugin/impl/trigger.py", line 35, in fetch_trigger_providers

    response: list[PluginTriggerProviderEntity] = self._request_with_plugin_daemon_response(

                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/plugin/impl/base.py", line 210, in _request_with_plugin_daemon_response

    raise e

  File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response

    response.raise_for_status()

  File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status

    raise HTTPStatusError(message, request=request, response=self)

httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers?page=1&page_size=256'

For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404)

2025-11-01 08:29:25.092 ERROR [Dummy-24] [app.py:875] - Exception on /console/api/workspaces/current/triggers [GET]

Traceback (most recent call last):
@crazywoola commented on GitHub (Nov 3, 2025): @dosu > ``` > 2025-11-01 08:29:25.092 ERROR [Dummy-24] [base.py:209] - Failed to request plugin daemon, status: 404, url: plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers > > Traceback (most recent call last): > > File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response > > response.raise_for_status() > > File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status > > raise HTTPStatusError(message, request=request, response=self) > > httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers?page=1&page_size=256' > > For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404) > > 2025-11-01 08:29:25.092 ERROR [Dummy-24] [app.py:875] - Exception on /console/api/workspaces/current/triggers [GET] > > Traceback (most recent call last): > > File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 917, in full_dispatch_request > > rv = self.dispatch_request() > > ^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/.venv/lib/python3.12/site-packages/flask/app.py", line 902, in dispatch_request > > return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args) # type: ignore[no-any-return] > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/.venv/lib/python3.12/site-packages/flask_restx/api.py", line 404, in wrapper > > resp = resource(*args, **kwargs) > > ^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/.venv/lib/python3.12/site-packages/flask/views.py", line 110, in view > > return current_app.ensure_sync(self.dispatch_request)(**kwargs) # type: ignore[no-any-return] > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/.venv/lib/python3.12/site-packages/flask_restx/resource.py", line 41, in dispatch_request > > resp = meth(*args, **kwargs) > > ^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/controllers/console/wraps.py", line 219, in decorated > > return view(*args, **kwargs) > > ^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/libs/login.py", line 80, in decorated_view > > return current_app.ensure_sync(func)(*args, **kwargs) > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/controllers/console/wraps.py", line 36, in decorated > > return view(*args, **kwargs) > > ^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/controllers/console/workspace/trigger_providers.py", line 50, in get > > return jsonable_encoder(TriggerProviderService.list_trigger_providers(user.current_tenant_id)) > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/services/trigger/trigger_provider_service.py", line 61, in list_trigger_providers > > return [provider.to_api_entity() for provider in TriggerManager.list_all_trigger_providers(tenant_id)] > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/core/trigger/trigger_manager.py", line 135, in list_all_trigger_providers > > return cls.list_plugin_trigger_providers(tenant_id) > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/core/trigger/trigger_manager.py", line 57, in list_plugin_trigger_providers > > provider_entities = manager.fetch_trigger_providers(tenant_id) > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/core/plugin/impl/trigger.py", line 35, in fetch_trigger_providers > > response: list[PluginTriggerProviderEntity] = self._request_with_plugin_daemon_response( > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File "/app/api/core/plugin/impl/base.py", line 210, in _request_with_plugin_daemon_response > > raise e > > File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response > > response.raise_for_status() > > File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status > > raise HTTPStatusError(message, request=request, response=self) > > httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/ad147542-8ad6-4c79-ba41-e6339b43820e/management/triggers?page=1&page_size=256' > > For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404) > > 2025-11-01 08:29:25.092 ERROR [Dummy-24] [app.py:875] - Exception on /console/api/workspaces/current/triggers [GET] > > Traceback (most recent call last): > ```
Author
Owner

@dosubot[bot] commented on GitHub (Nov 3, 2025):

The 500 Internal Server Error is caused by the plugin daemon returning a 404 for the /management/triggers endpoint of the plugin ID ad147542-8ad6-4c79-ba41-e6339b43820e. This happens because trigger providers are not implemented or registered in the current Dify architecture—the plugin daemon does not have a handler for this endpoint, so any request to list triggers for a plugin will fail with a 404 and result in a backend error see code details.

To resolve this, you can:

  • Avoid using features or workflow nodes that depend on plugin triggers until support is added in Dify.
  • Check your workflow and plugin configuration to ensure you are only using supported provider types (tools, datasources).
  • If you believe the plugin should provide triggers, verify its installation and registration, but note that the backend currently lacks trigger provider support.

If you need trigger functionality, you may want to follow Dify updates or contribute to the implementation of trigger providers in the plugin daemon. For now, this error is expected behavior due to missing backend support for triggers.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 3, 2025): <!-- Answer --> The 500 Internal Server Error is caused by the plugin daemon returning a 404 for the `/management/triggers` endpoint of the plugin ID `ad147542-8ad6-4c79-ba41-e6339b43820e`. This happens because trigger providers are not implemented or registered in the current Dify architecture—the plugin daemon does not have a handler for this endpoint, so any request to list triggers for a plugin will fail with a 404 and result in a backend error [see code details](https://github.com/langgenius/dify/blob/7a81e720d440f9f83897839f10bce4ff96628bfa/api/core/plugin/impl/base.py#L33-L323). To resolve this, you can: - Avoid using features or workflow nodes that depend on plugin triggers until support is added in Dify. - Check your workflow and plugin configuration to ensure you are only using supported provider types (tools, datasources). - If you believe the plugin should provide triggers, verify its installation and registration, but note that the backend currently lacks trigger provider support. If you need trigger functionality, you may want to follow Dify updates or contribute to the implementation of trigger providers in the plugin daemon. For now, this error is expected behavior due to missing backend support for triggers. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/079b1d43-9d59-4ab7-bcc8-c8617a8689a5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/079b1d43-9d59-4ab7-bcc8-c8617a8689a5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/079b1d43-9d59-4ab7-bcc8-c8617a8689a5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/079b1d43-9d59-4ab7-bcc8-c8617a8689a5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/079b1d43-9d59-4ab7-bcc8-c8617a8689a5?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/079b1d43-9d59-4ab7-bcc8-c8617a8689a5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/079b1d43-9d59-4ab7-bcc8-c8617a8689a5?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27713)
Author
Owner

@AreChen commented on GitHub (Nov 5, 2025):

^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/controllers/console/workspace/trigger_providers.py", line 50, in get

    return jsonable_encoder(TriggerProviderService.list_trigger_providers(user.current_tenant_id))

                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/services/trigger/trigger_provider_service.py", line 61, in list_trigger_providers

    return [provider.to_api_entity() for provider in TriggerManager.list_all_trigger_providers(tenant_id)]

                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/trigger/trigger_manager.py", line 135, in list_all_trigger_providers

    return cls.list_plugin_trigger_providers(tenant_id)

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/trigger/trigger_manager.py", line 57, in list_plugin_trigger_providers

    provider_entities = manager.fetch_trigger_providers(tenant_id)

                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/plugin/impl/trigger.py", line 35, in fetch_trigger_providers

    response: list[PluginTriggerProviderEntity] = self._request_with_plugin_daemon_response(

                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/app/api/core/plugin/impl/base.py", line 210, in _request_with_plugin_daemon_response

    raise e

  File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response

    response.raise_for_status()

  File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status

    raise HTTPStatusError(message, request=request, response=self)

httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/6a40f7ef-aabd-4c3f-b249-da577116f025/management/triggers?page=1&page_size=256'

For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404)

same issue

@AreChen commented on GitHub (Nov 5, 2025): ``` ^^^^^^^^^^^^^^^^^^^^^ File "/app/api/controllers/console/workspace/trigger_providers.py", line 50, in get return jsonable_encoder(TriggerProviderService.list_trigger_providers(user.current_tenant_id)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/services/trigger/trigger_provider_service.py", line 61, in list_trigger_providers return [provider.to_api_entity() for provider in TriggerManager.list_all_trigger_providers(tenant_id)] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/trigger/trigger_manager.py", line 135, in list_all_trigger_providers return cls.list_plugin_trigger_providers(tenant_id) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/trigger/trigger_manager.py", line 57, in list_plugin_trigger_providers provider_entities = manager.fetch_trigger_providers(tenant_id) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/plugin/impl/trigger.py", line 35, in fetch_trigger_providers response: list[PluginTriggerProviderEntity] = self._request_with_plugin_daemon_response( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/api/core/plugin/impl/base.py", line 210, in _request_with_plugin_daemon_response raise e File "/app/api/core/plugin/impl/base.py", line 207, in _request_with_plugin_daemon_response response.raise_for_status() File "/app/api/.venv/lib/python3.12/site-packages/httpx/_models.py", line 763, in raise_for_status raise HTTPStatusError(message, request=request, response=self) httpx.HTTPStatusError: Client error '404 Not Found' for url 'http://plugin_daemon:5002/plugin/6a40f7ef-aabd-4c3f-b249-da577116f025/management/triggers?page=1&page_size=256' For more information check: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404⁠](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404) ``` same issue
Author
Owner

@abby12006 commented on GitHub (Nov 10, 2025):

@yumilious
Hi! What is the version of the dify-plugin-daemon in your current docker-compose.yaml file?
I have changed it to dify-plugin-daemon version and docker compose pull, the Internal Server Error no longer appears
version ↓↓↓↓
image: langgenius/dify-plugin-daemon:main-local

@abby12006 commented on GitHub (Nov 10, 2025): @yumilious Hi! What is the version of the dify-plugin-daemon in your current docker-compose.yaml file? I have changed it to dify-plugin-daemon version and docker compose pull, the Internal Server Error no longer appears version ↓↓↓↓ image: langgenius/dify-plugin-daemon:main-local
Author
Owner

@yumilious commented on GitHub (Nov 10, 2025):

plugin_daemon:
   image:langgenius/dify-plugin-daemon:0.3.3-local
   restart: always
  db:
    image: postgres:15-alpine
    restart: always
    environment:
      POSTGRES_USER: ${POSTGRES_USER:-postgres}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-difyai123456}
      POSTGRES_DB: ${POSTGRES_DB:-dify}
      PGDATA: ${PGDATA:-/var/lib/postgresql/data/pgdata}
    command: >
      postgres -c 'max_connections=${POSTGRES_MAX_CONNECTIONS:-100}'
               -c 'shared_buffers=${POSTGRES_SHARED_BUFFERS:-128MB}'
               -c 'work_mem=${POSTGRES_WORK_MEM:-4MB}'
               -c 'maintenance_work_mem=${POSTGRES_MAINTENANCE_WORK_MEM:-64MB}'
               -c 'effective_cache_size=${POSTGRES_EFFECTIVE_CACHE_SIZE:-4096MB}'
               -c 'statement_timeout=${POSTGRES_STATEMENT_TIMEOUT:-60000}'
               -c 'idle_in_transaction_session_timeout=${POSTGRES_IDLE_IN_TRANSACTION_SESSION_TIMEOUT:-60000}'
    volumes:
      - ../.data/dify/volumes/db/data:/var/lib/postgresql/data
    healthcheck:
      test:
        [
          "CMD",
          "pg_isready",
          "-h",
          "db",
          "-U",
          "${PGUSER:-postgres}",
          "-d",
          "${POSTGRES_DB:-dify}",
        ]
      interval: 1s
      timeout: 3s
      retries: 60

  # The redis cache.
  redis:
    image: redis:6-alpine
    restart: always
    environment:
      REDISCLI_AUTH: ${REDIS_PASSWORD:-difyai123456}
    volumes:
      # Mount the redis data directory to the container.
      - ../.data/dify/volumes/redis/data:/data
    # Set the redis password when startup redis server.
    command: redis-server --requirepass ${REDIS_PASSWORD:-difyai123456}
    healthcheck:
      test:
        [
          "CMD-SHELL",
          "redis-cli -a ${REDIS_PASSWORD:-difyai123456} ping | grep -q PONG",
        ]

  # The DifySandbox
  sandbox:
    image: langgenius/dify-sandbox:0.2.12
    restart: always
    environment:
      # The DifySandbox configurations
      # Make sure you are changing this key for your deployment with a strong key.
      # You can generate a strong key using `openssl rand -base64 42`.
      API_KEY: ${SANDBOX_API_KEY:-dify-sandbox}
      GIN_MODE: ${SANDBOX_GIN_MODE:-release}
      WORKER_TIMEOUT: ${SANDBOX_WORKER_TIMEOUT:-15}
      ENABLE_NETWORK: ${SANDBOX_ENABLE_NETWORK:-true}
      HTTP_PROXY: ${SANDBOX_HTTP_PROXY:-http://ssrf_proxy:3128}
      HTTPS_PROXY: ${SANDBOX_HTTPS_PROXY:-http://ssrf_proxy:3128}
      SANDBOX_PORT: ${SANDBOX_PORT:-8194}
      PIP_MIRROR_URL: ${PIP_MIRROR_URL:-}
    volumes:
      - ../.data/dify/volumes/sandbox/dependencies:/dependencies
      - ../.data/dify/volumes/sandbox/conf:/conf
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8194/health"]
    networks:
      - ssrf_proxy_network

  # plugin daemon
  plugin_daemon:
    image: langgenius/dify-plugin-daemon:0.3.3-local
    restart: always
    environment:
@yumilious commented on GitHub (Nov 10, 2025): ``` plugin_daemon: image:langgenius/dify-plugin-daemon:0.3.3-local restart: always ``` ``` db: image: postgres:15-alpine restart: always environment: POSTGRES_USER: ${POSTGRES_USER:-postgres} POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-difyai123456} POSTGRES_DB: ${POSTGRES_DB:-dify} PGDATA: ${PGDATA:-/var/lib/postgresql/data/pgdata} command: > postgres -c 'max_connections=${POSTGRES_MAX_CONNECTIONS:-100}' -c 'shared_buffers=${POSTGRES_SHARED_BUFFERS:-128MB}' -c 'work_mem=${POSTGRES_WORK_MEM:-4MB}' -c 'maintenance_work_mem=${POSTGRES_MAINTENANCE_WORK_MEM:-64MB}' -c 'effective_cache_size=${POSTGRES_EFFECTIVE_CACHE_SIZE:-4096MB}' -c 'statement_timeout=${POSTGRES_STATEMENT_TIMEOUT:-60000}' -c 'idle_in_transaction_session_timeout=${POSTGRES_IDLE_IN_TRANSACTION_SESSION_TIMEOUT:-60000}' volumes: - ../.data/dify/volumes/db/data:/var/lib/postgresql/data healthcheck: test: [ "CMD", "pg_isready", "-h", "db", "-U", "${PGUSER:-postgres}", "-d", "${POSTGRES_DB:-dify}", ] interval: 1s timeout: 3s retries: 60 # The redis cache. redis: image: redis:6-alpine restart: always environment: REDISCLI_AUTH: ${REDIS_PASSWORD:-difyai123456} volumes: # Mount the redis data directory to the container. - ../.data/dify/volumes/redis/data:/data # Set the redis password when startup redis server. command: redis-server --requirepass ${REDIS_PASSWORD:-difyai123456} healthcheck: test: [ "CMD-SHELL", "redis-cli -a ${REDIS_PASSWORD:-difyai123456} ping | grep -q PONG", ] # The DifySandbox sandbox: image: langgenius/dify-sandbox:0.2.12 restart: always environment: # The DifySandbox configurations # Make sure you are changing this key for your deployment with a strong key. # You can generate a strong key using `openssl rand -base64 42`. API_KEY: ${SANDBOX_API_KEY:-dify-sandbox} GIN_MODE: ${SANDBOX_GIN_MODE:-release} WORKER_TIMEOUT: ${SANDBOX_WORKER_TIMEOUT:-15} ENABLE_NETWORK: ${SANDBOX_ENABLE_NETWORK:-true} HTTP_PROXY: ${SANDBOX_HTTP_PROXY:-http://ssrf_proxy:3128} HTTPS_PROXY: ${SANDBOX_HTTPS_PROXY:-http://ssrf_proxy:3128} SANDBOX_PORT: ${SANDBOX_PORT:-8194} PIP_MIRROR_URL: ${PIP_MIRROR_URL:-} volumes: - ../.data/dify/volumes/sandbox/dependencies:/dependencies - ../.data/dify/volumes/sandbox/conf:/conf healthcheck: test: ["CMD", "curl", "-f", "http://localhost:8194/health"] networks: - ssrf_proxy_network # plugin daemon plugin_daemon: image: langgenius/dify-plugin-daemon:0.3.3-local restart: always environment: ```
Author
Owner

@minodisk commented on GitHub (Nov 21, 2025):

I was in the same situation, but updating the langgenius/dify-plugin-daemon version to 0.4.1-local fixed it.
See docker-compose.yml for v1.10.0 😉

@minodisk commented on GitHub (Nov 21, 2025): I was in the same situation, but updating the `langgenius/dify-plugin-daemon` version to `0.4.1-local` fixed it. See [docker-compose.yml](https://github.com/langgenius/dify/blob/1.10.0/docker/docker-compose.yaml#L808) for v1.10.0 😉
Author
Owner

@yumilious commented on GitHub (Nov 25, 2025):

Thank you! I've already got v1.10 up and running—much appreciated.

@yumilious commented on GitHub (Nov 25, 2025): Thank you! I've already got v1.10 up and running—much appreciated.
Author
Owner

@WeiLinJoe commented on GitHub (Dec 16, 2025):

same problem
but updating the langgenius/dify-plugin-daemon version to 0.5.1-local fixed it.
See docker-compose.yml for v1.11.0

thx a lot 👍🍑🍑

@WeiLinJoe commented on GitHub (Dec 16, 2025): same problem but updating the langgenius/dify-plugin-daemon version to 0.5.1-local fixed it. See [docker-compose.yml](https://github.com/langgenius/dify/blob/1.11.0/docker/docker-compose.yaml#L910) for v1.11.0 thx a lot 👍🍑🍑
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#20071