Merge pull request #38 from ringcentral/logIdNullHandling

Handle Case when CallLog Creation failed and logId is null
ringcentral · Jul 5, 2024 · 71e3e85 · 71e3e85
2 parents e434189 + 1dc7814
commit 71e3e85
Showing 1 changed file with 9 additions and 7 deletions.
diff --git a/src/core/log.js b/src/core/log.js
@@ -69,13 +69,15 @@ async function createCallLog({ platform, userId, incomingData }) {
             name: incomingData.contactName ?? ""
         };
         const { logId, returnMessage } = await platformModule.createCallLog({ user, contactInfo, authHeader, callLog, note, additionalSubmission });
-        await CallLogModel.create({
-            id: incomingData.logInfo.id,
-            sessionId: incomingData.logInfo.sessionId,
-            platform,
-            thirdPartyLogId: logId,
-            userId
-        });
+        if (!!logId) {
+            await CallLogModel.create({
+                id: incomingData.logInfo.id,
+                sessionId: incomingData.logInfo.sessionId,
+                platform,
+                thirdPartyLogId: logId,
+                userId
+            });
+        }
         return { successful: true, logId, returnMessage };
     } catch (e) {
         console.log(`Error: status: ${e.response?.status}. data: ${e.response?.data}`);