From f6fa24de2b3bae4686a799a8b349c7a3e45f0d1f Mon Sep 17 00:00:00 2001
From: saptarshi-bose <67792552+saptarshi-bose@users.noreply.github.com>
Date: Wed, 11 Feb 2026 18:19:44 +0530
Subject: [PATCH] adjusted zoho Token expiry time to miliseconds. (#27855)

The Date.now() method returns time in epoch miliseconds, adding 60 * 60 = 3.6seconds leads to a bug that results in expiring the access token in 3.6 seconds, although it been valid. It creates unnecessary api calls to the zoho servers before most the api calls.
---
 packages/app-store/zohocrm/lib/CrmService.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/app-store/zohocrm/lib/CrmService.ts b/packages/app-store/zohocrm/lib/CrmService.ts
index 1bdf522a35..22f58d1545 100644
--- a/packages/app-store/zohocrm/lib/CrmService.ts
+++ b/packages/app-store/zohocrm/lib/CrmService.ts
@@ -236,7 +236,7 @@ class ZohoCrmCrmService implements CRM {
         );
         if (!zohoCrmTokenInfo.data.error) {
           // set expiry date as offset from current time.
-          zohoCrmTokenInfo.data.expiryDate = Math.round(Date.now() + 60 * 60);
+          zohoCrmTokenInfo.data.expiryDate = Math.round(Date.now() + 60 * 60 * 1000);
 
           await prisma.credential.update({
             where: {