Just to close off the topic and for future reference, I couldn’t find any issues with the configuration, but WATO was still showing the error. I activated the changes on the command line on the distributed site, then cleared the contents of the replication_changes file for the distributed site under “var/check_mk/wato/” on the master.
Subsequent activations in WATO have gone through without issue.