#1676: fix graceful handling of "key not found" error for journey and…

… event
Accenture · Sep 5, 2024 · 04754c8 · 04754c8
1 parent 41a9454
commit 04754c8
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/lib/metadataTypes/Event.js b/lib/metadataTypes/Event.js
@@ -42,10 +42,10 @@ class Event extends MetadataType {
      * @param {string} [key] customer key of single item to retrieve
      * @returns {Promise.<MetadataTypeMapObj>} Promise of metadata
      */
-    static retrieve(retrieveDir, _, __, key) {
+    static async retrieve(retrieveDir, _, __, key) {
         Util.logBeta(this.definition.type);
         try {
-            return super.retrieveREST(
+            return await super.retrieveREST(
                 retrieveDir,
                 `/interaction/v1/eventDefinitions${
                     key ? '/key:' + encodeURIComponent(key) : ''

diff --git a/lib/metadataTypes/Journey.js b/lib/metadataTypes/Journey.js
@@ -185,7 +185,7 @@ class Journey extends MetadataType {
             // if the interaction does not exist, the API returns an error code which would otherwise bring execution to a hold
             if (
                 [
-                    'Journey matching key not found.',
+                    'Interaction matching key not found.',
                     'Must provide a valid ID or Key parameter',
                 ].includes(ex.message)
             ) {