How to implement message retry through service-api? There is no parent_message_id field

[woo-hoo110]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

How to implement message retry through service-api? There is no parent_message_id field

[dosubot[bot]]

I found discussions and issues that might be helpful:

• [https://github.com/The latest version of dify. Does the chat messages API still support the parent_cessage_id parameter. Based on the already replied answer, regenerate the answer #13733] The latest version of dify. Does the chat messages API still support the parent_cessage_id parameter. Based on the already replied answer, regenerate the answer.

• [https://github.com/How to implement message retry through service-api? There is no parent_message_id field #18076] How to implement message retry through service-api? There is no parent_message_id field. The suggested solution involves using other fields like id, conversation_id, status, and error to implement message retry logic effectively.