We are using new feature Supplemental ID When we try to deploy the Journey we are getting error alert
an't resolve multiple reentrance journey version '36429d7d-ab35-450f-8f25-09ae6ce51742': Only multiple reentrance event allowed. (ERR_AUTHORING_JOURNEYVERSION_360 )
Why we are getting this
Solved! Go to Solution.
Views
Replies
Total Likes
Adobes response to the issue -
One guardrail/limitation is that when an event with a supplemental ID is used, all downstream events should also use a supplemental ID of the same namespace.
As we have more than one events in the journey and only one of them has a supplemental ID defined while the other does not, this is the reason for the error while publishing the journey. Adding the same supplemental ID as the initial event in the subsequent events will resolve the issue.
Warm Regards,
Reena John
Can you try to uncheck allow reentrance checkbox on the journey details and see if the error goes off. We tried and it hasnt worked for us.
This seems to be an issue on the supplemental id, we are also facing the issue and have reached out to Adobe support team on the same. Will keep you posted on the teams response.
Adobes response to the issue -
One guardrail/limitation is that when an event with a supplemental ID is used, all downstream events should also use a supplemental ID of the same namespace.
As we have more than one events in the journey and only one of them has a supplemental ID defined while the other does not, this is the reason for the error while publishing the journey. Adding the same supplemental ID as the initial event in the subsequent events will resolve the issue.
Warm Regards,
Reena John
@Poornaraj_Duraimani
If you need concurrent instances per profile:
1. Edit the first Event activity.
2. Tick Use supplemental identifier and select the attribute (e.g. booking ID, order ID).
3. Or switch to a Business Event and enable Allow multiple executions.
If you don’t need concurrent instances:
1. Open the Journey properties panel.
2. Disable the Multiple re-entrance option (leave the standard re-entrance setting or turn it off entirely). After aligning the re-entrance setting with an eligible event trigger, the journey should validate and publish without ERR_AUTHORING_JOURNEYVERSION_360.
References:
• Supplemental identifier & multiple entrances – https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/manage-journ...