Records not injected to Journey Builder from Sales

• Which version of the Marketing Cloud Connect package is being used? 
  • The top way to avoid known bugs is to stay up to date with the most recent release of the Installed Package. You can check your version by clicking 'Setup' in Sales. Next travel to, 'Build' > Installed Packages. The package is named 'Marketing Cloud'. The most recent version is documented on this page.
• Does my Marketing Cloud API User have access to the Object/Records that are being updated/created?
  • Since the Marketing Cloud API User is used to maintain the integration between Sales and Marketing Cloud, this User will need access to any record which is intended to inject to Journey Builder through the integration. This is done by integrating the Marketing Cloud API User with a Salesforce User (typically the dedicated Salesforce System User that has the proper permissions for each object. Providing the System Administrator Role to this Salesforce User is an easy way to ensure this is correct.
• Ensure Tenant-Specific OAuth Endpoints are enabled in your connected Salesforce org. See Enabling Tenant-Specific OAuth Endpoints for Marketing Cloud Connect for more information.
  
  
• Please make sure flows are active in Salesforce CRM org which are created/updated by creating journey into marketing cloud. For example: If we have created journey based on Lead object then go to setup of CRM and type flows in quick finds then look for flows JBSystemFlow_Lead & JBSystem_Lead_RecordFlow which should be active.
• Are records able to be injected under the most simple Entry Criteria, with no Related Object Criteria applied? 
  • In some cases, Entry Criteria is too exclusive or includes two filters which conflict with each other. For example if the Primary Object is set to Lead, and Entry Criteria is configured to inject once 'Lead:Status' is updated to ['Pending' AND 'Closed'] these two criteria would not allow records to inject. The 'Status' of a Lead can only be one or the other, so if you were to replace the AND with an OR operator then you would increase the chances of successful injection. 
  • If the Criteria required for your live deployment is robust and includes many filters, but injection has not taken place after updating or creating a record, attempt to take all Criteria away except for a single filter. Once injection is successful through the single filter, gradually work up to a complex filter. This practice will identify problematic filters explicitly. This can be applied through Related Object Criteria application as well. 
  • If the 'Update/Create' action is being completed through a Form Submission or a separate Process, verify that the 'Updated/Created' record contains the required data to satisfy the Entry Criteria after the Process has completed. In some cases the separate Process will 'Update/Create' a record with only a portion of the data required, and an additional Process needs to run to complete the record.
    • An example of this scenario could be a Form Submission of a customer who is requesting white pages about your business happens at 6pm EST. Upon submission, they are added to your CRM as a Lead. Their Lead record contains details about their request. It may be expected that this record injects shortly after 6pm EST. However, within Process Builder there is a scheduled process which updates newly created Leads each morning at 5am EST. One of the fields which is updated by this Process is included as Entry Criteria for your Journey. So injection should not be expected until shortly after 5am EST, rather than immediately when the Form is submitted. 
  • The field type of Sales fields included in the 'Criteria' can impact if injection will be successful. Formula field types will not trigger based on an 'Update'. Since formula types are dependent on other fields, they are unable to satisfy the state change of 'not qualifying', to 'qualifying'. This state change is required in order to qualify as an 'Update' action. Formula field types will trigger injection when 'Create' is the action used. The state change is explained in greater detail below.
• How the 'Action' choice plays a role in triggering injection.
  • Example Salesforce Entry Event configuration:

Object: Opportunity
Who : LeadID (Lead)
Action : Updated
Criteria : 'Opportunity:Lead:FirstName' equals 'James' AND ('Opportunity:Status' equals 'Won' OR 'Opportunity:Status' equals 'Pending')

• The 'Update' Action type only injects records that newly meet entry criteria upon evaluation.
  • We create an Opportunity tied to a Lead for James Dean, with Status = 'Pending'. This does not trigger injection because 'Action' is set to Update and created records are not evaluated.
  • Later, we update the Opportunity for James Dean, setting Status to 'Won'. This also does not trigger injection because the record already met criteria before the update, and only records that newly meet criteria are injected by the Update action type.
• Let's continue using the same Entry Event Configuration and our Lead, James Dean. In this scenario we want James to inject to our Journey two times. Once when his Opportunity Status equals 'Pending' and then a second time once it is updated to 'Won'. We create an Opportunity for James and the status is equal to 'Waiting'. This does not trigger injection. A few days pass and now the Opportunity record is updated to 'Pending.' James is now injected to the Journey. Our team continues to work on winning the Opportunity and eventually they do. The Opportunity Status is now changed to 'Won.' Injection does not take place. Our crucial requirement for Update to trigger injection is for the record to not qualify and then be updated to a state of qualifying, and this did not take place. Our Opportunity had a Status of 'Pending' and then was updated to 'Won.' Both of which qualify so the system does not register this as an Update. Within Entry Criteria, each filter component can be thought of as grouped into a single filter. Sending a record against this filter either returns a 1 (true) or 0 (false). If the record qualifies then a 1 is sent. If the record is updated in a way which it continues to qualify then a 1 is sent. In order for the update to satisfy the Entry Criteria Action of Update, a 0 must be passed between each 1. If you require updates such as this to result in multiple injections, then you could create two Journeys, one for Opportunity Status of 'Won' and a second for Opportunity Status of 'Pending.' 

Additional Resources:  

• Parse debug logs when Salesforce Data does not inject into Journey