Goal is in Journey Builder using SF Data Entry Event on standard SF Task object, once updated to match criteria - to enter the related Person Account Contact to Journey.
On Task there are two lookup fields, one to Person Account and second to Person Account Contact. Have tried injecting the Contact via both ways.
Based on documentation Configure Events for Person Account Related Objects, the requirement is that the object record is updated to match the criteria.
Example setup is that once Task status is changed to Priority: High, the linked Contact enters Journey. Initially the Task is created as Priority: Normal and then priority is updated as a separate action.
Currently no matter what kind of setup I do with Task and related Account/Contact, nothing enters Journey. By using Account or Contact object as primary object via SF Entry Event, it all works.
Is the documentation missing some requirements?
Here's the current version Entry Source: