Date in message scenario for activity moved is displayed as 3000-01-01

Summary:

The date field in message scenario shows 3000-01-01 instead of the date.

Content (please ensure you mask any confidential information):

I have configured a message scenario with the launch condition set to "Activity Created". To prevent multiple notifications for segmentable activities, I added a Blocking Condition:
"Activity Type [appt_type] In (multiday_activity_segment)".

This successfully prevents multiple notifications for activity segments. However, I noticed that the dates are appearing as 3000-01-01, even though the activity is properly scheduled and not placed in the unscheduled pool. This is same even if I move the activity between unscheduled pool to resource or even if I change the scheduled activity from one date to another.