🐛 Fix: Handle NoSyncToken error during gcal notification

logs instead message instead of full error to signify that this is a known scenario and not something we need to do anything about

Author: tyler-dane

packages/backend/src/common/constants/error.constants.ts

@@ -186,7 +186,7 @@ export const SyncError = {
   },
   NoSyncToken: {
     description: "No syncToken",
-    status: Status.NO_CONTENT,
+    status: Status.INTERNAL_SERVER,
     isOperational: true,
   },
   NoEventChanges: {

packages/backend/src/sync/controllers/sync.controller.ts

@@ -2,7 +2,10 @@ import { Request } from "express";
 import { Status } from "@core/errors/status.codes";
 import { Logger } from "@core/logger/winston.logger";
 import { Payload_Sync_Notif } from "@core/types/sync.types";
-import { UserError } from "@backend/common/constants/error.constants";
+import {
+  SyncError,
+  UserError,
+} from "@backend/common/constants/error.constants";
 import {
   isFullSyncRequired,
   isInvalidGoogleToken,
@@ -61,6 +64,18 @@ class SyncController {
         res.status(Status.OK).send(result);
         return;
       }
+      if (
+        e instanceof Error &&
+        e.message === SyncError.NoSyncToken.description
+      ) {
+        logger.debug(
+          `Ignored notification due to missing sync token for resourceId: ${resourceId}`,
+        );
+        // returning 204 instead of 500 so client doesn't
+        // attempt to retry
+        res.status(Status.NO_CONTENT).send();
+        return;
+      }
 
       logger.error("Not sure how to handle this error:");
       logger.error(e);