create less Sentry errors when google calendar fetching fails

tourlane · Sep 14, 2024 · 3b997e0 · 3b997e0
1 parent 0715324
commit 3b997e0
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/packages/app-store/googlecalendar/lib/CalendarService.ts b/packages/app-store/googlecalendar/lib/CalendarService.ts
@@ -62,7 +62,6 @@ export default class GoogleCalendarService implements Calendar {
         // `Failed to refresh access token for Google Calendar: userId: ${credential.userId}`
         // );
         this.log.error("Error refreshing google token", err);
-        Sentry.captureException(err);
       }
       return myGoogleAuth;
     };

diff --git a/packages/core/CalendarManager.ts b/packages/core/CalendarManager.ts
@@ -187,12 +187,17 @@ export const getBusyCalendarTimes = async (
       calendars: selectedCalendars,
       credentials: withCredentials,
     });
+    /**
+    * Do not send this to Sentry. It's kind of an expected error that happens when a user is leaves Tourlane
+    * for example but they are still on Calcom.
+    *
     Sentry.captureException(error, {
       extra: {
         calendars: selectedCalendars,
         credentials: withCredentials,
       },
     });
+    */
   }
   return results.reduce((acc, availability) => acc.concat(availability), []);
 };