Missing ops trace task when chat message generation fails

### 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.15.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When starting a chat with a chatbot or agent, the model provider returns an error and doesn’t send the ops trace task. ### ✔️ Expected Behavior Even if the LLM returns an error, the ops trace task should still be sent. ### ❌ Actual Behavior _No response_