About journeys in Automation
In order for journeys to appear in Automation’s audit log, the configuration of your journey type is also rendered within Automation’s rule builder. This means that although you configure your journey within Journeys, it also gets captured in Automation as this is what is powering it behind-the-scenes. This includes each version of a journey type that you publish.
If you need to make configuration changes to a journey type, you should perform this in Journeys. This is because any changes or action taken on a journey type in Automation can’t be synced in Journeys, and may cause your journey type to no longer work as expected.
Although you may be able to delete, disable or even make edits to your journey type within the context of Automation, these changes can’t be synced in Journeys. This means that once a journey type is republished within the journey builder, any edits made within the rule builder won’t be applied, as publishing will create a new version and disable all previous versions to prevent multiple executions.
Delete a journey type in Automation
This will stop new journeys and in-progress journeys from executing, and your journey type be removed from Automation’s rule list. As journey types cannot be permanently deleted; only removed from your Automation’s rule list, your journey type may still appear as published in Journeys due to the inability to sync.
Disable a journey type in Automation
This will only stop new journeys from triggering, and all in-progress journeys will continue to run as expected. However, your journey type may still appear as published in Journeys due to the inability to sync.
Enable a journey type in Automation
This will trigger new journeys, however if it’s a previously disabled rule, this may cause double executions of multiple journey versions concurrently which may affect JQL queries and reports. Your journey type may also still appear as archived in Journeys due to the inability to sync.
この内容はお役に立ちましたか?