← All posts
Guide

LINE Rich Menu Still Showing? Clear Defaults and Unlink Users

A LINE rich menu can remain visible after you clear the default because a per-user menu has higher priority, another default remains configured, or the open chat has not refreshed. Deleting the menu object is not the same as unlinking it from a user. Identify the active assignment first, remove it through the correct management surface, and verify the chat display before deleting unused assets.

Key takeaways

  • Check per-user assignments before changing defaults again.
  • Manage LINE Official Account Manager settings in Manager, not through the Messaging API.
  • Unlink per-user menus before deleting their objects when you need the open chat to change.
  • For tabbed menus, stop alias-based switching before unlinking, then check for residual links.

Which rich menu is actually being displayed?

LINE’s rich menu overview defines this priority, from highest to lowest:

PriorityAssignmentDiagnostic implication
HighestPer-user rich menu set through the Messaging APIClearing the default does not remove this assignment
NextDefault rich menu set through the Messaging APIRemoving a higher-priority assignment can reveal this menu
LowestDefault rich menu set through LINE Official Account ManagerCheck Manager as well if the goal is no menu at all

Distinguish replace the campaign menu from show no rich menu. Unlinking a personalized menu can correctly reveal a default; that is not necessarily a failed unlink. A no-menu target requires checking all applicable layers.

If several systems manage the account, name one owner for this change. Our multiple-tools checklist explains the shared configuration boundary. As an operational precaution, pause your own menu-assignment jobs during retirement so they do not restore a configuration you just removed.

Match the removal method to the assignment

The official stop-displaying guide separates these operations:

What you need to removeCorrect controlWhat to verify
Messaging API defaultClear default rich menuRe-enter the chat; the change may take about a minute to apply
Manager-created defaultChange or delete the setting in ManagerRe-enter the chat; the Messaging API cannot stop this Manager setting
Per-user assignmentUnlink the rich menu from the target user or usersCheck the affected user and any default that becomes visible
Unneeded menu objectDelete rich menu after display removal is confirmedDo not use object deletion as proof of immediate disappearance

LINE says per-user setting changes take effect immediately, but deleting the object without unlinking leaves it visible in an already-open chat until the user re-enters. Bulk operations also need their own completion checks; do not interpret a submitted batch as every screen having changed.

For testing, use the mobile LINE chat. The overview states that rich menus are not displayed on LINE for PC, so an empty desktop view cannot validate mobile retirement.

Retire tabbed menus without leaving a user linked

Tabbed menus introduce another cause of inconsistent results. LINE’s tab-switching guide explains that switching tabs creates a per-user menu state. Clearing the original default therefore does not remove the menu that user sees.

The stop-displaying guide recommends this order:

  1. Delete the relevant rich menu aliases so users cannot switch to another tab during unlinking.
  2. Unlink the target menus from users, using the appropriate operation, such as Replace or unlink the linked rich menus in batches.
  3. Wait, then run the unlinking process again to clear links that remained because of tab switching.
  4. Confirm that the menus are no longer displayed, then delete the unneeded menu objects.

LINE does not specify a fixed waiting interval in this guidance. Do not invent one as a completion guarantee. Deleting aliases temporarily prevents tab switching, so plan the user experience and communicate that transition to the support team.

Before starting, retain the intended fallback, menu configuration, and assignment information needed for recovery. This is a recommended change-management record, not a LINE-provided rollback transaction.

Keep menu retirement separate from message intake

A menu-display change is not a webhook migration. Leave the receiving workflow alone unless changing it is a separate approved task. Our rich menu insights article distinguishes menu analytics from incoming customer messages; neither click totals nor a successful message receipt proves that a menu disappeared.

UnifyPort’s unofficial interface provides a separate connected-account messaging path, not LINE Official Account rich-menu management. The LINE authorization reference documents QR authorization, with QR URL and PIN delivered asynchronously through webhooks. It is not a way to clear a Manager default or unlink an Official Account menu. Keep those actions in LINE’s official tools.

FAQ

Why does another menu appear after unlinking?

A lower-priority default may now be visible. Check both the Messaging API default and the Manager default against the intended final state.

Is deleting a rich menu enough to hide it immediately?

No. LINE documents that an already-open chat can continue displaying a deleted menu until the user re-enters. For per-user menus, unlink first.

Why do only some users still see the old menu?

Compare per-user assignments, whether users switched tabs, and whether they re-entered the chat. Different display states do not by themselves prove an API failure.

Next step and sources

Start with LINE’s stop-displaying procedure. Record the desired final display, test a user with a per-user menu and one without, and check both open and re-entered chats before deleting assets. These are proposed acceptance checks, not reported test results.

Official sources checked on 2026-11-16:

UnifyPort API

Turn messaging integration into a stable product pipeline.

Start by sending through one API, then bring every inbound message back into your business system with standard events.