I managed to look at Whatsapp logs on windows 11 and this could be the most possible failure reason. If someone has a case with Whatsapp, feel free to add it as extra info
[FG W P:19912 T:025040 D:21 01-05-24 00:55:12.374 ERROR] Exception: DateTimeConvertor/EnsureIsSeconds > Unix Timestamp supposed to be seconds is too long
at WhatsApp.DateTimeConvertor.EnsureIsSeconds(Int64) + 0x65
at WhatsApp.Sync.History.PayloadProcessor.SetInitialConvoDetails(IMessagesContext, Conversation, Conversation, Boolean) + 0x1f0
at WhatsApp.Sync.History.PayloadProcessor.<>c__DisplayClass19_0.<TryProcessInitialBootStrap>b__0(IMessagesContext) + 0x45e
at WhatsApp.Data.DbAccessProviderExtensions.Run[TDbAccess](IDbAccessProvider`2, Action`1, String) + 0x67
at WhatsApp.Sync.History.PayloadProcessor.TryProcessInitialBootStrap(HistorySync, HistorySyncChunkStatus, String) + 0x1ca
at WhatsApp.Sync.History.PayloadProcessor.ProcessInitialBootStrap(HistorySync, HistorySyncChunkStatus, String) + 0x5e
at WhatsApp.Sync.History.PayloadProcessor.ProcessHistorySyncPayload(HistorySyncChunkStatus) + 0xbd
at WhatsApp.Sync.History.PayloadProcessor.ProcessPayloads() + 0xcf
at WhatsApp.Sync.History.PayloadProcessor.<>c__DisplayClass15_0.<ScheduleProcessingImpl>b__0() + 0x34
at WhatsApp.DispatcherExtensions.InvokeAction(Object) + 0x35
at System.Threading.ContextCallback.InvokeOpenStaticThunk(Object) + 0x22
at WhatsApp.ConcurrentQueueDispatcher.InvokeQueueItems(Object) + 0x112
at System.Threading.QueueUserWorkItemCallbackDefaultContext.<>c.<.cctor>b__5_0(Object) + 0x46
at System.Threading.ExecutionContext.RunInternal(ExecutionContext, ContextCallback, Object) + 0xc6
at System.Threading.ExecutionContext.Run(ExecutionContext, ContextCallback, Object) + 0xf
at System.Threading.QueueUserWorkItemCallbackDefaultContext.ExecuteWorkItem() + 0x50
at System.Threading.ThreadPoolWorkQueue.Dispatch() + 0x1c8
at System.Threading.ThreadPool.DispatchCallback(IntPtr, IntPtr, IntPtr) + 0x4b