Truncate statement runs on slave replica for a table that is ignored for replication

We recently had an issue with our replication failing due to a truncate statement replicating to the slave RDS instance, despite the database the truncate statement is in is ignored in replication using replicate-ignore-db. I have looked for an answer as to why and what we could to to prevent this but I haven’t been able to find anything. Any help/advice would be greatly appreciated.

We currently use AWS RDS using MySQL version 8.0.35.

How was the DDL formatted? TRUNCATE TABLE db.tableX; or use db; TRUNCATE TABLE tableX;

TRUNCATE TABLE db.tableX;

And on the RDS replica, when you do SHOW REPLICA STATUS\G, you can see db listed on ignore?

Yes, it is definitely there.

Have you reproduced this with another table? Can you create a dummy table in the same DB and reproduce?