@Ajo_WisdomChase This issue seems to be a bug. Open a ticket with Adobe support. For now, the workaround is duplicating the fragment and updating it.

@harishdev You can't trigger a journey externally unless if you're using events you can achieve this.  https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configuration/configure-journeys/events-journeys/about-events

@DavidKangni I get that feedback dataset will no longer supported with streaming segmentation only. But still, you can use batch audiences using feedback dataset if that's a desired option as opposed to putting on daily cap business rules depending on the requirement.

@BrandonDa6 You can have an audience created using (AJO Message Feedback Event Schema) the messages received from a journey and exclude that in the campaign audience you're setting up. path: _experience.customerJourneyManagement.messageDeliveryfeedback.feedbackStatus_experience.customerJourneyManage...

@Caveman77 It's good that you're collaborating with Adobe support to sort things out. You maybe doing this already. If you're thinking about copying the journey, just try duplicating it and make the necessary updates.

@RyleeCl Can you try duplicating the fragment, remove the condition, add again then publish the fragment to see if that works?

@SanmathiKumar Lookup tables are only supported on events at this point. Currently events lookup schema is available to use in the journeys (conditions, custom actions, etc.) and message personalization. You can open a ticket with Adobe support and ask to submit an enhancement request by providing t...

@AliKh2 No, you can't restore the journey once it has been deleted.

@Dnelson_WG There are a couple of ways to handle this.  Update the data import workflow to have prefix 1 on the mobile number while importing the data into ACS.If the above can't be done use a separate workflow to pull the records having mobile numbers and use update activity to update the mobile nu...

@amijain You can do this via edge decisioning. Take a look at this documentation.