Schedule for running Journey shows as 'Not Yet Scheduled'
Last updated 2020-05-14 ·Reference W-7346448 ·Reported By 8 users
The schedule of a running Journey shows the text 'Not Yet Scheduled'. When this issue occurs, although the Journey schedule appears as if it is not configured, this is just an issue on the UI and the Journey should still inject records when the Automation associated with the Journey runs.
Note: This issue has only been reported for Journeys using the Data Extension entry source and occurs only when using the Automation schedule type. As this issue has been linked to a code change was applied to fix a Query Activity bug, the automation used in the Journey schedule should also contain a Query Activity that targets the Journey entry data extension.
This issue is not reproducible when creating a new Journey. It has only been observed in long running Journeys mostly created prior to September 2019.
The workaround advised is to re-save the Query Activity in the Automation that targets the Journey entry source data extension as follow:
-Navigate to Journey Builder > Automation Studio
-Open the Activities tab, click on SQL QUERY and search for the name of the query contained in the Journey Automation.
-Open the Query Activity.
-Click the Edit button.
-Navigate through the wizard without making any changes but pressing Next > Next > Next > Finish.
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.