Wallet worker not restarting after node WebSocket reconnection

[jhlee-young]

Summary of Bug

When the relayer node’s WebSocket connection drops and later reconnects, the wallet worker responsible for telemetry stops running and never restarts. This leads to missing telemetry data after a reconnect event. The issue seems to occur consistently after a disconnection and reconnection sequence.

Version

hermes version 1.13.2

Steps to Reproduce

1. Start Hermes normally with telemetry.enabled true.
2. Disconnect the WebSocket endpoint of one of the connected nodes.
3. Wait until Hermes reconnects to the node.
4. Observe that:

• The relayer resumes packet relaying as expected.
• However, telemetry logs from the wallet worker stop appearing.
• The wallet worker process does not restart automatically.

Acceptance Criteria

• Stopped telemetry worker which query nodes automatically restarts and resumes output after a node WebSocket reconnect.
• No manual restart of Hermes is required for telemetry recovery

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate milestone (priority) applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned