Clarification on Dispatcher Flush agent triggers

[Abhilasha_S]

I have set up the dispatcher flush agent on the publisher. Can someone explain what “on Receive” means and what “chain replication” means in this context?
There is no official documentation explaining chain replication, which makes it very confusing.
Is anyone using this setting and explain the chain replication thing? 
Can chain replication cause any performance issues if used on production sites?

[giuseppebag]

hi @Abhilasha_S, 

“On Receive” tells a replication agent to run when the local instance receives a replication event, and in practice it is used to “chain” a second replication action (for example, a Dispatcher flush) immediately after content arrives on Publish so cache invalidation happens only after new content is in place. “Chain replication” in this context simply means one replication event triggers another agent on the receiving side, most commonly Author → Publish (content) followed by Publish → Dispatcher (flush), and this pattern is standard and recommended for production.

Adobe’s Dispatcher flushing guide shows the end‑to‑end flow and recommends enabling “On Receive” on the Publish flush agent so invalidation occurs only after content arrives on Publish, illustrating the chain behavior in production topologies.