Our planning agent fills the calendar from a topic list. It keeps scheduling the same topic two weeks apart with a slightly different title, so it looks varied and is not.
We tried telling it not to repeat topics. It does not think it is repeating, because the titles differ.
Give every topic an ID and make it schedule IDs, not titles. Titles come afterwards.
Give it the published list, not the plan. Ours double-booked because it was reading what we intended, not what we did.
And have it check titles against the query clusters. If two slots map to the same cluster, one of them is a duplicate in disguise.
And let it see the last eight weeks, not just the future. It cannot avoid a repeat it cannot see.
Content marketing manager, new. We solved it badly: a person checks. Then we solved it properly: the agent lists the three nearest existing pieces before it proposes a new one.
Analyst here, new. If you log what was published with the topic ID you can also see which topics actually performed, which is the next question anyway.
IDs plus the eight-week window fixed it. Logging by ID now as well, thanks.