Modifying an Automation concurrently reverts changes
Last updated 17 days ago ·Reference W-8932188 ·Reported By 1 users
No Fix
Summary
An Automation can have its workflow or settings changed if it is being worked on concurrently, likely through it being open in multiple tabs of a browser, and reflect the original state rather than the updated state.
This can impact Journey Builder and injections from a Data Extension.
Repro
A Journey Builder Repro example:
- Create Automation1 With Query Activity that inserts into TargetDE
- Configure Journey with Automation schedule using Automation1
- Publish Journey
- Open Automation1 in Automation studio (observe the new JB activity)
- Stop Journey Version 1
- Create Journey Version 2
- Delete/recreate entry source on Journey Version 2 to use Automation1
- Publish Journey Version 2
- NOTE: at this point, Automation 1 should be correctly pointed at the new entry source configured on Version 2
- Go back to Automation1 that is already open and click Save again
- NOTE: The automation will be overwritten by it's previous state
Workaround
Work within one tab of a browser when making changes within the Marketing Cloud
Reported By (1)
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.
