Client's Table Triggers Unexpected Waterfall, Consuming Credits

One of our client's table triggered a waterfall that was not supposed to be triggered, and consumed dozens of credits. This is the table: https://app.clay.com/workspaces/48060/tables/t_Ci3WndguPDEa/views/gv_8d4keBcEXuqe We put a condition in place for the first enrichment of the waterfall, but it didn't prevent the following enrichments from running. We enriched for private emails.