Enabling mySQL replication using GTID after purging binlog
Whether you use GTID or not, any replica needs a continuous stream of binlogs to keep in sync.
If any of the binlogs needed for the replica to catch up are gone, then it's trash. It can never catch up.
You need to reinitialize the replica. As if you were creating a new replica: make a new backup from the master, and use it to overwrite the replica. Then the replica can catch up from the point you created the backup.