Test mode converts date/time to local machine time
Last updated 2020-06-15 ·Reference W-6873981 ·Reported By 3 users
Fixed in version Marketing Cloud Release May 2020
Test mode converts date/time fields in data extensions to local machine time.This can cause confusion around decision splits or entry filters as it may appear that records meet or don't meet criteria, but then go down the incorrect decision split path.
-Change your local machine time to Eastern Standard Time.
-Go to Journey Builder > Create Journey From Scratch
-Drag a Data Extension Entry Event onto canvas and configure it with a Data Extension that has a date field
-Drag a decision split onto the canvas
-Configure it to use the Data Extension in the entry event
-Configure it to be date field equal to a date (could be any date)
-Configure the rest of the journey to completion, save
-Go to Contact Builder > Data Extensions > Find your Event Data Extension or Data Extension used in Contact Data
-Add records to it. Make sure one is equal to the date mentioned in your filter (it will default to a timestamp of 00:00:000)
-Go back to Journey Builder > Your Journey > Validate > Test
-Select a record that meets criteria > note it goes down the "YES" path Also Note that the timestamp is 2:00am
-On your local machine, change your time zone to Pacific Standard Time
-Open an incognito/private window > login to the same account and perform the same test with the same record
-Note that the date/time is the previous day at 11pm
-Note that it still goes down the YES path despite not meeting criteria
The date/time used will be whatever exists in the data extension within Contact Builder and not the converted value in Journey Test Mode.
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.