Mysql replication error 13121 after upgrades to Mysql 8 (no replies)

Has anyone encounter this on their Mysql slave and have any workaround? My master and slave was replicating fine until I upgraded to 8, now i sporadically get this error and do a "start slave" and it goes back to normal until it happens again. Not sure if it's a config setting i'm missing but i have plenty of other setup like this that did not give me any slaving replication errors.

Tried to look up the error but previous 8.0.28 have said it was a bug and fixed and i'm upgrading to mysql 8.0.39 so not sure what to do. The slave binlog_format is row. I have tried to fix including rebuilding the slave 3 times and resetting the slave position (stop slave,reset slave all, change master command). I assume could be binlog corruption but it moves on to next binlog on master like it did before fine, nothing was changed other than upgrading both master and slave to 8.0.39

Here's a snippet of the error it stop at and I try to look at the mysqlbinlog on master position and slave position

connect_Retry: 60
Master_Log_File: mysqld-bin.000624
Read_Master_Log_Pos: 313510668
Relay_Log_File: xxx-relay-bin.000005
Relay_Log_Pos: 3403228
Relay_Master_Log_File: mysqld-bin.000624
Slave_IO_Running: Yes
Slave_SQL_Running: No
Last_Errno: 13121
Last_Error: Relay log read failure: Could not parse relay log
event entry. The possible reasons are: the source's binary log is corrupted
(you can check this by running 'mysqlbinlog' on the binary log), the replica's
relay log is corrupted (you can check this by running 'mysqlbinlog' on the
relay log), a network problem, the server was unable to fetch a keyring key
required to open an encrypted relay log file, or a bug in the source's or
replica's MySQL code. If you want to check the source's binary log or replica's
relay log, you will be able to know their names by issuing 'SHOW REPLICA STATUS'
on this replica.