Loading

Marketing Cloud Engagement | Journey Builder 1-Month Wait Activity Behavior for Non-Existent Dates

Fecha de publicación: Feb 19, 2026
Descripción

When the duration for a Journey Builder Wait Activity is set to 1 month, the wait typically ends on the same day of the following month. This article details how the system automatically adjusts the end date to the last day of the month when the start date, such as the 31st, does not exist in the subsequent month. This information is intended for Marketing Cloud Engagement administrators managing journey schedules.

Solución

When a 1-month duration is configured in a Journey Builder [Wait Activity], the end date is calculated based on the calendar day of the following month relative to when the contact reached the activity.

 

Basic Calculation Rules for Wait End Dates

Wait duration calculations are based on calendar dates rather than a fixed number of days such as 30 days.

The wait ends at the same time on the same day of the following month.

*Example: If a contact starts the wait on October 23, the wait ends on November 23.

 

Behavior for Month-End Start Dates

When a wait begins on a date that does not exist in the following month, the system adjusts the end date to the final day of that month.

 

Case 1: 1-Month Wait Starting on January 30

Because February does not have a 30th day, the last day of February becomes the end date.

  1. Identify if the current year is a common year or a leap year.

  2. In a common year, the wait ends on February 28.

  3. In a leap year, the wait ends on February 29.

 

Case 2: 1-Month Wait Starting on March 31

Because April only has 30 days and no 31st day exists, the last day of April becomes the end date.

  1. Identify that the following month is April.

  2. Confirm April ends on the 30th.

  3. Set the end date to April 30.

Número del artículo de conocimiento

005315468

 
Cargando
Salesforce Help | Article