Bug type

Behavior bug (incorrect output/state without crash)

Summary

Title: LINE webhook route intermittently returns 404 until gateway restart (2026.3.2)

Summary: On macOS LaunchAgent gateway (loopback:18789), LINE channel shows running/configured, but GET /line/webhook intermittently returns 404. LINE webhooks via ngrok then get 404 and no sessions are created. openclaw gateway restart immediately restores /line/webhook to 200.

Steps to reproduce

[ ] openclaw gateway restart
[ ] sleep 2 && curl -i http://127.0.0.1:18789/line/webhook

Expected behavior

/line/webhook should remain reachable while LINE channel is running.

Actual behavior

Body (copy/paste):
Version: OpenClaw 2026.3.2 (85377a2)
OS: macOS (LaunchAgent service: ai.openclaw.gateway.plist)
Gateway: bind loopback, port 18789
Channel: LINE plugin (line, accountId=default), running/configured=true
Symptom: /line/webhook intermittently returns 404:
curl -i http://127.0.0.1:18789/line/webhook → 404 Not Found
At the same time, openclaw channels status --json shows line running/configured true (no lastError)
openclaw channels logs --channel line --lines 200 shows repeated [default] starting LINE provider (Steve hair) with no clear channel exited / auto-restart attempt
When this happens, LINE webhooks via ngrok receive POST /line/webhook 404
Workaround: openclaw gateway restart immediately restores GET /line/webhook → 200 OK (and LINE works again)
Expected: /line/webhook should remain reachable while LINE channel is running.

OpenClaw version

ersion: OpenClaw 2026.3.2 (85377a2)

Operating system

macOS

Install method

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response