0

We have one Journey whose Entry Source is DE.The DE gets overwritten using a SQL from Automation. The records which are processed by journey wouldnot be picked up by SQL again. We have noticed that their are some older records which are not yet injected into Journey and they are coming into Entry DE. As per Journey Contacts Evaluation tab , Journey rejected these contacts.

What could be the reason for Journey not processing certain records as entry DE is overwritten by SQL on scheduled interval.

How can this issue be resolved?

Improve this question
6
  • It can be your Contacts re-entry mode in Journey settings. Are you by any chance using No re-entry mode?
    – Rachid Mamai
    Nov 20, 2019 at 9:18
  • We are using option Re-entry anytime.
    – Sushant Edlabadkar
    Nov 20, 2019 at 9:20
  • Do you have any additional filtering set up on entry criteria in JB?
    – Lukas Lunow
    Nov 20, 2019 at 9:25
  • No We don't have any additional filter ,We are facing this issue randomly with some records and once the record is not injected then whenever it comes as SQL result output in next automation run it is not injected again into Journey.
    – Sushant Edlabadkar
    Nov 20, 2019 at 9:45
  • 1
    Is this anything to do with 'High-water-mark' !..... I guess as you are using the OVERWRITE option, the journey is NOT able to figure out the respective contact has already entered the journey or not!...... Because the OVERWRITE option will delete the hidden attribute set by journey to determine this... If I am confusing please refer this link --- success.salesforce.com/answers?id=9063A000000pl5dQAA
    – Vishal Kumar C V
    Nov 20, 2019 at 14:19

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .