Merge pull request #1930 from Accenture/bug/1836-transactional-send-j…

…ourneys-cannot-be-versioned-or-updated-if-activepublished bug/1836 Ensure automatic new version creation only happens to multi-step jourmeys without a draft version
Accenture · Dec 13, 2024 · 9e9ddd8 · 9e9ddd8
2 parents 2e3ebe7 + 75d5e66
commit 9e9ddd8
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/@types/lib/metadataTypes/Journey.d.ts.map b/@types/lib/metadataTypes/Journey.d.ts.map
diff --git a/lib/metadataTypes/Journey.js b/lib/metadataTypes/Journey.js
@@ -1609,7 +1609,11 @@ class Journey extends MetadataType {
             );
             const cachedVersion = cache.getByKey(this.definition.type, normalizedKey);
             if (cachedVersion) {
-                if (cachedVersion.status === 'Draft') {
+                if (
+                    cachedVersion.status === 'Draft' ||
+                    cachedVersion.definitionType !== 'Multistep'
+                ) {
+                    // we can update journeys either if there is a draft version or if the type is not multistep. transactional and quicksend journeys do not have versions.
                     // add version to ensure we update the correct one
                     metadataMap[metadataKey].version = cachedVersion.version;
                     // update modifiedDate field to bypass API-error "Another user recently modified this journey. Refresh to edit the latest version."