In my situation it made more sense to instead ignore the table doesn’t exist errors. It is because my database system has little to no chance of ever changing and the updates in question never target the tables I am replicating.
It is a legacy system that we’re slowly moving away from.
slave-skip-errors=1146
The only other reliable way to solve this would be to switch to row-level bin logging on the master, however I couldn’t get them to make that change for me.
solved Mysql replication with UPDATE JOIN on an ignored table