Software agent error reveals distinction between publishing and listing events

A scheduled publishing agent failed to detect three existing posts because its duplicate-checking mechanism conflated two separate events. The agent checked a listing endpoint, which returned a complete-looking list that omitted the three most recent posts, even though they had been live for over six hours. The root cause was using the same term 'published' for both the immediate write event and the later indexing event, which updates on an independent schedule. This made the agent treat the listing's answer about index freshness as a definitive answer about what had been published. The solution involves the publishing job creating its own synchronous record of work, making the remote listing a secondary check rather than the primary source of truth.