When using the LINE (GroupConnect) feature in Marketing Cloud Engagement (MCE), if the monthly message limit (contract plan sending limit) of the destination LINE Official Account is reached, the LINE API returns a limit-exceeded response and subsequent sends fail. Because no error message indicating this cause appears in the management UI, the issue may appear to users as "sends appear to be processing normally, but messages are not delivered."
At end of month, inquiries about messages or Automations that were previously sending successfully suddenly failing are frequently attributable to this issue. If you encounter a similar issue, follow the steps below to triage and investigate.
Method : Simple Message Send
First, send a simple message — plain text only, with no AMP script or other content — to a test recipient on the LINE account to triage the issue.
If the message sent during this test is not delivered despite the recipient not having blocked the LINE Official Account, the monthly sending limit described above may have been reached. In that case, check the current month's message send count for the target LINE Official Account and compare it against the contract plan limit.
If the limit has not been reached and a simple text message from GroupConnect still cannot be sent, contact support with details including the date and time the sending failure was confirmed.
Important: Notes on test sends
When testing, do not use Journey Builder or Automation. Instead, go directly to Mobile Studio > [GroupConnect] and create and send a single Outbound Message. This ensures the test is not affected by factors other than the message sending function itself. In particular, Journey Builder shares Job IDs across journeys, so send failures may be caused by issues unrelated to LINE sending — such as stalled sends in other journeys, or Journey Builder contact entry and progress issues.
005321987

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.