Dify 1.9.0: session.app.chat.invoke() causes invalid input syntax for type uuid: "DEFAULT-USER" #18321

Closed
opened 2026-02-21 19:46:15 -05:00 by yindo · 0 comments
Owner

Originally created by @yt-koike on GitHub (Sep 26, 2025).

Originally assigned to: @laipz8200, @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.9.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Install an Endpoint plugin and execute self.session.app.chat.invoke() in it. In my case, I used https://marketplace.dify.ai/plugins/yt-koike/cron.

✔️ Expected Behavior

The specified app should be invoked without errors. I tested that Dify 1.8.1 can execute self.session.app.chat.invoke() well.

Actual Behavior

When the plugin executes invoke(), it returns an error which says Internal Server Error: invoke app failed: request failed with status code: 400 and respond with: {"code":"invalid_param","message":"user not found","status":400}.
In Dify's docker compose logs, Dify records the following error.

db-1 | 2025-09-26 12:03:15.082 UTC [1562768] ERROR: invalid input syntax for type uuid: "DEFAULT-USER" at character 471 
db-1 | 2025-09-26 12:03:15.082 UTC [1562768] STATEMENT: SELECT end_users.id AS end_users_id, end_users.tenant_id AS end_users_tenant_id, end_users.app_id AS end_users_app_id, end_users.type AS end_users_type, end_users.external_user_id AS end_users_external_user_id, end_users.name AS end_users_name, end_users.is_anonymous AS end_users_is_anonymous, end_users.session_id AS end_users_session_id, end_users.created_at AS end_users_created_at, end_users.updated_at AS end_users_updated_at
db-1 | FROM end_users
db-1 | WHERE end_users.id = 'DEFAULT-USER'::UUID AND end_users.tenant_id = '25633d38-cf86-4217-902a-8731d3152a6b'::UUID
db-1 | LIMIT 1

Regarding the log, I presume it is because Dify 1.9.0 does not have DEFAULT-USER anymore.

Originally created by @yt-koike on GitHub (Sep 26, 2025). Originally assigned to: @laipz8200, @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.9.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Install an Endpoint plugin and execute self.session.app.chat.invoke() in it. In my case, I used https://marketplace.dify.ai/plugins/yt-koike/cron. ### ✔️ Expected Behavior The specified app should be invoked without errors. I tested that Dify 1.8.1 can execute self.session.app.chat.invoke() well. ### ❌ Actual Behavior When the plugin executes invoke(), it returns an error which says `Internal Server Error: invoke app failed: request failed with status code: 400 and respond with: {"code":"invalid_param","message":"user not found","status":400}`. In Dify's docker compose logs, Dify records the following error. ``` db-1 | 2025-09-26 12:03:15.082 UTC [1562768] ERROR: invalid input syntax for type uuid: "DEFAULT-USER" at character 471 db-1 | 2025-09-26 12:03:15.082 UTC [1562768] STATEMENT: SELECT end_users.id AS end_users_id, end_users.tenant_id AS end_users_tenant_id, end_users.app_id AS end_users_app_id, end_users.type AS end_users_type, end_users.external_user_id AS end_users_external_user_id, end_users.name AS end_users_name, end_users.is_anonymous AS end_users_is_anonymous, end_users.session_id AS end_users_session_id, end_users.created_at AS end_users_created_at, end_users.updated_at AS end_users_updated_at db-1 | FROM end_users db-1 | WHERE end_users.id = 'DEFAULT-USER'::UUID AND end_users.tenant_id = '25633d38-cf86-4217-902a-8731d3152a6b'::UUID db-1 | LIMIT 1 ``` Regarding the log, I presume it is because Dify 1.9.0 does not have DEFAULT-USER anymore.
yindo added the 🐞 bug label 2026-02-21 19:46:15 -05:00
yindo closed this issue 2026-02-21 19:46:15 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#18321