Loading

Marketing Cloud Engagement | Journey Builder: LINE Message Delivery Order Behavior

Publiseringsdato: Jan 29, 2026
Beskrivelse
When LINE message activities are placed consecutively on a Journey Builder canvas, the order in which messages arrive on the recipient's device is not guaranteed.
For example, even if [Message B] is placed immediately after [Message A], Message B may arrive first — or at the same time — making the order appear reversed.

 

Root Cause: Asynchronous Processing and LINE Platform Behavior
This behavior is caused by the internal processing order in Marketing Cloud Engagement and LINE platform behavior.
  1. Asynchronous processing within Marketing Cloud Engagement
    Journey Builder activity processing and the actual message send process run asynchronously. After a contact passes through an activity, each request is processed independently. Depending on resource availability and processing timing, a later message may complete processing first.
  2. LINE platform behavior
    Even if Marketing Cloud Engagement sends API requests in the correct order, the LINE platform's own processing conditions may cause messages to arrive on the end user's device out of order.
Løsning

Resolution 1: Use a Multi-Content Message

To reliably deliver multiple elements — such as text, images, and stickers — in a specific order (for example, an image immediately after text), strongly consider combining them as multi-content within a single LINE message.
  • How to configure: When creating a LINE message in Content Builder, add multiple bubbles (up to 5) within the message creation screen.
  • Note: Carousels cannot be used within a multi-content message.
 

Resolution 2: Control Timing with a Wait Activity

When preserving delivery order is required, insert a Wait activity between each message activity to explicitly separate processing timing.

Example configuration steps:
  1. Open the target journey in Journey Builder.
  2. Place the first message activity (for example, LINE Message A).
  3. Place a Wait activity immediately after it.
  4. Set the wait duration to a value sufficient for the system to complete processing (for example, 1 minute or a specific duration).
    • Note: Results may vary depending on system load, but adding even a minute-level interval increases the likelihood that the previous message send process completes before the next one begins.
  5. Place the second message activity (for example, LINE Message B) after the Wait activity.
This configuration increases the likelihood that the first message send process runs ahead of the second, reducing the risk of reversed delivery order on the recipient's device.

Important (Trade-off): Applying this workaround introduces a delay of the configured wait duration (for example, 1 minute) between the arrival of the first and second messages. Note that messages will not arrive consecutively from the user's perspective — there will be a visible gap between them.
Knowledge-artikkelnummer

005239278

 
Laster
Salesforce Help | Article