how to... reset replication when only one schema stuffed

[ian diddams]

OS: centos 7
Mysql: 5.7.36

Slave-Master replication set up on two servers, a master and a slave.

We currently replicate "everything" - 39 schemas in total.

Quite often we notice that when replication breaks (for whatever reason) whilst we can usually fix it via the stop slave, skip 1, start slave style command sometimes for reasons aligned with devs changing collation character sets (zzzz) or similar this doesn't work and we have to reset replication from scratch - which takes several hours for a full dump on master and then import on live etc etc etc.

However we do notice that when this oddity occurs its only one schema that is actually affected ie has errors.

So instead of dumping all databases and copying them and importing them and resetting slaving configurations based on ,master status vat the time of the dump and so on...

is there a way to dump and import just the ONE schema and resetting whatever the master status info should be ?

Or is it really just as simple as a dump and import of the one schema and replication will just carry on regardless?

cheers

ian