[Chore] Incorrect exception handling in db query #15976

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

Originally created by @hyongtao-code on GitHub (Aug 7, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactoring, 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.

Description

The NotFound exception originates from Flask/Werkzeug and is used to handle HTTP 404 errors in web contexts. It is unrelated to SQLAlchemy and will never be raised by a database query. As a result, the original exception block was effectively dead code. As a result, actual database errors (e.g., connection issues, statement execution failures) were not caught or handled properly.

Motivation

No response

Additional Context

No response

Originally created by @hyongtao-code on GitHub (Aug 7, 2025). ### 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 refactoring, 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. ### Description The `NotFound` exception originates from `Flask/Werkzeug` and is used to handle HTTP 404 errors in web contexts. It is unrelated to SQLAlchemy and will never be raised by a database query. As a result, the original exception block was effectively dead code. As a result, actual database errors (e.g., connection issues, statement execution failures) were not caught or handled properly. ### Motivation _No response_ ### Additional Context _No response_
yindo closed this issue 2026-02-21 19:24:11 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#15976