openclaw - 💡(How to fix) Fix [Bug]: LINE channel status shows false warning despite valid token configured [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

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#68804Fetched 2026-04-19 15:07:14
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Timeline (top)
commented ×1

Error Message

  1. Observe LINE shows WARN despite working token

Fix Action

Workaround

None - the warning is cosmetic but confusing.

RAW_BUFFERClick to expand / collapse

Bug Description

LINE channel shows warning: "LINE channel access token not configured" even though the token is correctly configured and fully functional.

Steps to Reproduce

  1. Configure LINE channel with channelAccessToken and channelSecret in config
  2. Run openclaw status
  3. Observe LINE shows WARN despite working token

Expected Behavior

LINE channel should show OK when token is configured and functional.

Actual Behavior

  • LINE API works correctly (verified via curl to api.line.me)
  • LINE bot can send/receive messages
  • But status shows: "LINE channel access token not configured"

Investigation

The issue is in collectStatusIssues function in LINE plugin:

  • It expects accounts array format
  • But LINE config uses direct root-level format (channelAccessToken at channels.line.channelAccessToken)

This appears to be a mismatch between the status check logic and LINE's original config structure.

Environment

  • OpenClaw version: 2026.4.x
  • Channel: LINE
  • Config format: Direct (no accounts array)

Workaround

None - the warning is cosmetic but confusing.

extent analysis

TL;DR

The warning "LINE channel access token not configured" can be resolved by updating the collectStatusIssues function in the LINE plugin to accommodate the direct root-level format of the LINE config.

Guidance

  • Verify that the channelAccessToken is correctly set in the config file and that the LINE API is working as expected using tools like curl.
  • Investigate the collectStatusIssues function in the LINE plugin to understand how it expects the accounts array format and how it can be modified to support the direct root-level format used by the LINE config.
  • Consider updating the LINE config to use the accounts array format if possible, to align with the expected format of the collectStatusIssues function.
  • Review the OpenClaw documentation to see if there are any known issues or workarounds related to the LINE channel configuration.

Example

No code snippet is provided as the issue is related to the internal implementation of the collectStatusIssues function and the LINE plugin.

Notes

The issue appears to be specific to the OpenClaw version 2026.4.x and the LINE channel, and may not affect other channels or versions. The workaround is currently none, but updating the collectStatusIssues function or the LINE config format may resolve the issue.

Recommendation

Apply workaround: Update the collectStatusIssues function in the LINE plugin to support the direct root-level format of the LINE config, as this is a more targeted solution than changing the config format.

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…

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 channel status shows false warning despite valid token configured [1 comments, 2 participants]