Skip to main content

I created a copy of an automation that we are using with an active journey.  Whenever I made changes to the copy, the changes appeared in the original as well, and it resulted in the journey becoming disconnected from its data extension and contacts were no longer being entered into the journey.

 

I was able to fix things and get the journey back up and running, but I wasn't able to get a firm answer about whether it is safe to delete the copy of the automation without impacting the original automation.

 

Does anyone know what the implications are?

 

@* Marketing Cloud Engagement *

7 answers
  1. Jan 26, 2024, 8:18 AM

    If you have an original automation and a copy of that automation, deleting the copy generally shouldn't impact the original automation.  thewatchwrestling However, there are a few scenarios where there could be an impact:

    1. Dependencies: If the original automation and the copy share dependencies such as shared resources, data sources, or integrations, deleting the copy could potentially disrupt those dependencies. Make sure to review any dependencies before deleting the copy.
    2. Testing Environment: If the copy was serving as a testing or staging environment for changes before applying them to the original automation, deleting the copy would remove that testing environment. Ensure that any necessary testing has been completed before deleting the copy.
    3. Configuration Errors: If there were configuration errors or issues in the copy that were later corrected and applied to the original automation, deleting the copy could make it harder to troubleshoot or compare configurations.
    4. Documentation: If the copy contained documentation or annotations that were useful for understanding the original automation's purpose or configuration, deleting the copy could remove that documentation. Make sure to document any changes or important details elsewhere before deleting the copy.

    In general, if the copy of the automation is truly a duplicate with no active use or dependencies, deleting it shouldn't directly impact the original automation. However, it's always a good idea to review any potential impacts before deleting any part of your automation setup. 

0/9000