Marketing Cloud Engagement | Caution When Creating LINE Content for Journey Builder

LINE deliveries in Journey Builder are processed sequentially in a single internal queue. Multiple Journeys share this single queue for LINE delivery.
As a result, a LINE delivery error occurring in Journey A may impact a separate Journey B.

 

Understanding this behavior, when creating LINE content for delivery via Journey Builder, more thorough error handling and testing is required compared to LINE messages delivered through other channels or GroupConnect.

In particular, caution is required when using the RaiseError function, which allows users to intentionally trigger an error at any timing to forcibly terminate processing.

 

The second argument of the RaiseError function, boolSkipCurrentOnly (optional), controls behavior toward the next subscriber after an error occurs.

If a Job is halted due to RaiseError during LINE message delivery in Journey Builder, all Journey Builder LINE message deliveries to the same channel will be stopped, and there is a possibility that LINE message delivery in other Journeys will also stop. Currently, there is no way to detect this state via notifications or similar means. In rare cases, a Job halted by RaiseError may resume, causing all messages that had accumulated in the interim to be delivered at once. If a Job is halted, Technical Support must request manual resolution from the product team. (Resolution may take several days.)

Resolution:
There are two ways to avoid the issue: