Skip to content

fix(line): upgrade hardcoded error fallback to typed error routing #60813

Description

@garnetlyx

Problem

LINE is the only non-Telegram channel that sends a user-visible fallback message on dispatch failure, but it uses a hardcoded generic string via a bare try/catch rather than the typed error routing introduced for Telegram.

Current LINE fallback (src/line/monitor.ts):

"Sorry, I encountered an error processing your message."

This does not distinguish between rate limits, empty provider responses, or general errors.

Proposed fix

Replace the hardcoded fallback with the same resolveFailoverReasonFromError + EmptyResponseError routing used by Telegram, once the shared helper from #60812 is available.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions