openclaw - 💡(How to fix) Fix [Bug]: LINE plugin provider hangs at "start-account" phase — no inbound messages processed [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#78316Fetched 2026-05-07 03:38:18
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
2
Timeline (top)
labeled ×2commented ×1cross-referenced ×1mentioned ×1

LINE plugin provider hangs at "start-account" phase — no inbound messages processed. LINE webhook provider's startAccount() hangs at phase=channels.line.start-account indefinitely. Event loop delay reaches 4-7 seconds. Channel status shows running: true but lastInboundAt is never populated. Webhook POST from LINE returns 200 OK (ngrok), but messages are not processed as inbound events — agent never responds.

Error Message

  • No error logs from LINE plugin

Root Cause

LINE plugin provider hangs at "start-account" phase — no inbound messages processed. LINE webhook provider's startAccount() hangs at phase=channels.line.start-account indefinitely. Event loop delay reaches 4-7 seconds. Channel status shows running: true but lastInboundAt is never populated. Webhook POST from LINE returns 200 OK (ngrok), but messages are not processed as inbound events — agent never responds.

Code Example

[line] [default] starting LINE provider (น้องเก้า)
[diagnostic] liveness warning: reasons=event_loop_delay interval=30s
  eventLoopDelayMaxMs=4139.8 phase=channels.line.start-account

Channel status:
"line": {
  "configured": true,
  "running": true,
  "lastStartAt": 1778047314916,
  "lastStopAt": null,
  "lastError": null,
  "restartPending": false,
  "reconnectAttempts": 0
}

Token ok:
`curl https://api.line.me/v2/bot/info` returns 200 OK (bot info OK, userId, displayName: "น้องเก้า")

Related: #26478 (auto-restart, running:false); *this* case running:true but stuck at start-account, messages ignored.
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

LINE plugin provider hangs at "start-account" phase — no inbound messages processed. LINE webhook provider's startAccount() hangs at phase=channels.line.start-account indefinitely. Event loop delay reaches 4-7 seconds. Channel status shows running: true but lastInboundAt is never populated. Webhook POST from LINE returns 200 OK (ngrok), but messages are not processed as inbound events — agent never responds.

Steps to reproduce

  1. Install @openclaw/line plugin
  2. Configure channels.line with channelAccessToken + channelSecret + dmPolicy:"open"
  3. Set up ngrok/cloudflared tunnel to gateway
  4. Set LINE Dev Console webhook URL to tunnel URL
  5. Verify webhook (GET returns 200)
  6. Send a message from LINE app
  7. ngrok shows POST /line/webhook 200 OK
  8. Bot is silent — no reply in LINE app

Expected behavior

LINE bot should respond to messages after webhook verification.

Actual behavior

  • Gateway log: [line] [default] starting LINE provider (น้องเก้า)
  • Liveness warning every 30s: phase=channels.line.start-account
  • eventLoopDelayMaxMs=4000-6700ms
  • Channel status: running: true, lastInboundAt: never set
  • Despite 200 OK on webhook POST, inbound messages are not processed
  • No error logs from LINE plugin

OpenClaw version

2026.5.4

Operating system

Windows 10.0.26200 (x64)

Install method

npm global

Model

(Not specified, likely N/A for this repro)

Provider / routing chain

@openclaw/line (channels.line) direct -> gateway

Additional provider/model setup details

LINE plugin: @openclaw/line 2026.5.4 Channel config: dmPolicy:"open", other details per supplied params

Logs, screenshots, and evidence

[line] [default] starting LINE provider (น้องเก้า)
[diagnostic] liveness warning: reasons=event_loop_delay interval=30s
  eventLoopDelayMaxMs=4139.8 phase=channels.line.start-account

Channel status:
"line": {
  "configured": true,
  "running": true,
  "lastStartAt": 1778047314916,
  "lastStopAt": null,
  "lastError": null,
  "restartPending": false,
  "reconnectAttempts": 0
}

Token ok:
`curl https://api.line.me/v2/bot/info` returns 200 OK (bot info OK, userId, displayName: "น้องเก้า")

Related: #26478 (auto-restart, running:false); *this* case running:true but stuck at start-account, messages ignored.

Impact and severity

Affected: All LINE channel users on 2026.5.4 Severity: High (bot cannot receive/respond to inbound) Frequency: Always (reproducible every run) Consequence: LINE channels unusable for all communication

Additional information

Related issue: #26478 — prior issue caused fast restart-loops (running:false); this one enters running:true but channel never processes inbound events, webhook keeps returning 200.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

LINE bot should respond to messages after webhook verification.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: LINE plugin provider hangs at "start-account" phase — no inbound messages processed [1 comments, 2 participants]