openclaw - 💡(How to fix) Fix delivery-recovery on restart sends raw session context blob instead of original message [1 comments, 2 participants]

TL;DR

The issue can be mitigated by ensuring that the delivery recovery process correctly reconstructs the original pending delivery text instead of sending raw session context.

Guidance

• Verify that the config.patch triggered restart is properly handling the pending delivery queue, potentially by checking the queue's persistence and data integrity.
• Investigate the delivery recovery logic to determine why it's sending raw session context instead of the intended agent reply text, focusing on how the executor.ts source code is being incorporated into the message.
• Check the logging around delivery recovery to see if there are any indicators of data corruption or misinterpretation of the pending delivery content.
• Consider adding safeguards to the delivery recovery process to detect and handle cases where the original pending delivery text cannot be safely reconstructed, such as dropping the recovery or sending an error message.

Example

No code snippet can be provided without more context on the specific implementation details of the delivery recovery logic and how it interacts with the session context.

Notes

The exact cause of the issue is unclear without more information on the implementation of the delivery recovery process and how it handles pending deliveries during a gateway restart. The provided log evidence suggests that the recovery process is aware of the pending delivery but fails to correctly reconstruct its content.

Recommendation

Apply a workaround to the delivery recovery process to ensure it either delivers the correct pending agent reply text or drops the recovery if the content cannot be safely reconstructed, as the root cause of the issue is not immediately clear and may require further investigation.