I have a synchronized data extension that SQL queries Lead data into another data extension that is being used in a Journey.
The Journey sends out an initial email based on the status in the SQL query. A few days later, the journey makes a decision split where it looks at the status (via Contact Data) and sends a second email if its different from the first one.
The synchronized extension updates the status when it changes, but I see that when the query runs, it doesn't not make that status update in the other data extension.
Example: Lead A has a status of "Example A" in the synched extension. The query looks for those with "Example A" as their status and adds them to the "New" Data Extension and sends an email. Several days later Lead A has a status of "Example B" in the synched extension. This status is never updated in the "New" data extension even though the SQL query has an UPDATE data action. Lead A therefore does not move through the Journey to get the second email.
In this case, is the query wrong? Should be the Add or Overwrite action instead? I'm pretty stumped on what's going on.