Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Clarification on Dispatcher Flush agent triggers

Avatar

Level 2

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?

Abhilasha_S_0-1759328117896.png

 

2 Replies

Avatar

Level 10

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.

 

Avatar

Community Advisor

Hi @Abhilasha_S,

The replication agent will trigger when this instance receives a replication event.
For a Dispatcher flush agent on Publish, it ensures the cache is flushed after new content has actually arrived on Publish, not before.

“Chain replication” simply means one replication event triggers another - e.g. Author -> Publish (content) is followed by Publish -> Dispatcher (flush). This chaining is the standard way to keep Dispatcher caches in sync with content.

Performance impact: It’s a common and recommended setup in production. The only caution is that on very high-traffic sites with lots of activations, you can generate many flush requests, so monitor queues and avoid overly broad flush rules.

 


Santosh Sai

AEM BlogsLinkedIn