Publish and manage a Journey
Once your Journey is configured, publish it to start processing profiles. You can then pause or resume its execution and follow its lifecycle from the Journey header.
Before you publish
Before publishing, check three elements:
How the Journey accepts new profiles
How often it runs
Whether the Journey contains errors or warnings
Choose how profiles enter
Open Settings and configure the Enrollment section.
One time only
DinMo evaluates the entry rules during the first run. Profiles that qualify form the Journey's initial cohort. Later runs continue processing these profiles but do not enroll new ones.
Continuously
DinMo evaluates the entry rules during every run and enrolls newly eligible profiles.
For continuous enrollment, choose when DinMo should stop accepting new profiles:
Select Never to keep enrollment open.
Select At a specific time, then choose the date and time when enrollment should close.
The cutoff uses the workspace timezone. At or after this instant, new profiles cannot enter. Profiles already in the Journey continue until completion, after which the Journey turns Off. Changes take effect from the next Journey run. Moving the cutoff into the future can reopen enrollment while the Journey is still active. If the Journey is already Off, saving a later cutoff keeps it Off; use Restart after making the enrollment settings eligible.
Configure the processing schedule
The processing schedule determines how often DinMo evaluates and advances the Journey.
It is independent from enrollment. For example, an Always-on Journey can evaluate new profiles every hour or once per day.
Choose a schedule that matches the expected responsiveness of the Journey and the refresh frequency of its source data.
Resolve errors and review warnings
Select Publish to open the pre-publish checklist.
The checklist distinguishes between:
Error
Blocks publication and must be resolved.
Warning
Does not block publication but highlights a configuration that should be reviewed.
Select an issue to identify the affected step and update its configuration. You can also use View errors from the Journey header to reopen the list of blocking issues.
Warnings should only be accepted when the highlighted behavior is intentional. For example, DinMo may warn you when profiles are activated immediately after entering the Journey.
Publish the Journey
When the checklist contains no blocking errors, select Publish.
Publishing creates a new version of the Journey. This version becomes the configuration used by subsequent runs.
After publication:
DinMo starts running the Journey according to its schedule.
Profiles can enter according to the selected enrollment mode.
Profiles already in the Journey progress when its runs are processed.
The published version appears in the Journey's run history.
If you later update and republish the Journey, DinMo creates another version. Previous runs remain associated with the version that produced them.
Publishing can affect real profiles and destinations. Review the entry volume, activation steps, delays, branches, and exit rules before confirming.
Understand the Journey lifecycle
Enrollment and lifecycle are shown separately in DinMo.
One-time
The Journey accepts profiles during its initial enrollment run only.
Always on
The Journey continues accepting newly eligible profiles.
Draining
Enrollment is closed, but profiles are still progressing through the Journey.
Off
Enrollment is closed and no profiles remain active. Scheduled processing stops automatically.
A Journey enters Draining after the enrollment period ends—for example, after the initial enrollment of a One-time Journey or when an Always-on Journey reaches its configured end date.
While draining, no new profiles enter. Profiles already enrolled continue until they leave the Journey. DinMo moves the Journey to Off automatically when no active profiles remain.
Restart an Off Journey
An Off Journey can be restarted only when it uses continuous enrollment and its cutoff is set to Never or to a future date and time.
Update the enrollment settings if needed, then select Restart. Review the restart checklist and confirm Restart journey. DinMo makes the Journey Active again and resumes its scheduled runs.
Saving new settings alone does not restart an Off Journey.
Rename or duplicate a Journey
Rename a Journey
You can rename a Draft, Active, Draining, or Off Journey from its action menu. Enter a name of up to 100 characters.
Renaming changes the displayed name only. It does not unpublish the Journey, create a new version, change its schedule, reset active profiles, or remove its run history.
Duplicate a Journey
From the Journey list, open the source Journey's action menu, select Duplicate, enter a name, and confirm.
DinMo creates an independent Draft in the same Customer Hub. The copy includes the description, editable canvas, entry, re-entry and exit configuration, activation references, enrollment settings, and schedule. The copied schedule remains paused until the new Journey is published.
Runtime state is not copied: profiles, occurrences, counters, run history, output tables, and previously scheduled tasks remain attached to the source Journey. Review every referenced audience, destination, and date before publishing the copy. A copied enrollment cutoff in the past must be changed before publication.
Pause and resume execution
Pause a Journey when you need to temporarily stop its scheduled processing—for example, while investigating unexpected results or preparing a configuration change.
While the Journey is paused:
No scheduled runs are processed.
No new profiles enter.
Profiles already in the Journey do not progress.
Pausing does not reset the Journey or create a new enrollment cohort.
When you are ready to continue, select Resume. DinMo restarts processing according to the configured schedule and enrollment settings.
Before resuming, confirm that:
The reason for the pause has been resolved.
The Journey configuration is safe to run.
Profiles that were waiting can still continue with the expected timing.
Trigger a run manually
When Run now is available for your role, you can use it to trigger an execution without waiting for the next scheduled run.
A manual run does not change the Journey's enrollment mode or processing schedule. It follows the same rules as a scheduled run.
Use manual runs carefully: they can enroll, advance, or activate real profiles depending on the Journey configuration.
After publishing
After the first run:
Check that the run completed successfully.
Confirm that the number of enrolled profiles is consistent with your entry rules.
Review the current profile counts displayed on the Journey steps.
Verify that profiles reached the expected destinations.
Investigate errors before triggering another run.
Journey activity reflects the latest successfully completed run. It should not be interpreted as real-time data.
Related pages
Last updated