Unable to package Journey(s) using API Entry Event Referencing Journey Data in Entry Criteria
Last updated 2022-05-12 ·Reference W-10674500 ·Reported By 0 users
Journey Builder Journeys utilizing API Entry Events configured to use Journey Data in the Entry Event Filter Criteria will fail Package Manager Packaging with the error message 'Circular dependency'.
1) Navigate to JB -> Events -> Entry Source
2) Add a new API Event
3) Select DE
4) Select "Journey Data" under "Attributes"
5) Drag and drop any attribute to the filter
6) Use new entry source in a new Journey
7) Attempt to package Journey
8) Encounter error - 'Circular dependency'
Remove or Reconfigure the API Entry Event from the Journey(s) in question and attempt to package again. Once deployed, reconfigure the Journey entry event/entry criteria to fulfill desired use case.
Avoid using Journey Data in API Entry Events. Instead, pre-filter the attempted injection upstream, prior to initiating the API call to inject a record. This would entail only initiating the /interaction/v1/events route for contacts which contain data which would satisfy the logic that would have been included in the Entry Filter.
Reported By (0)
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.