[Dispatcher] - Whenever I publish a page, it triggers the replication of multiple other pages (not directly related) through the user "replication-service" | Community
Skip to main content
F
fbfr
Level 2
November 19, 2024

[Dispatcher] - Whenever I publish a page, it triggers the replication of multiple other pages (not directly related) through the user "replication-service"

  • November 19, 2024
  • 4 replies
  • 913 views

Hi,

As said in the title, whenever I publish a page it will trigger the replication of multiple other pages (children pages or not directly related pages) through the user "replication-service". It will overflow the Dispatcher Flush and a huge queueing of all the pages will appear on the publisher instance dispatcher.

All the configuration seems correct on both author and publish dispatcher.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 19, 2024

Hi, 


How did you ensure that those pages are not related? Can you reproduce this issue locally, or is it happening in a specific AEM instance/environment?

Esteban Bustamante
    F
    fbfrAuthor
    Level 2
    November 19, 2024

    Hi,

    Thanks for your input. I'm saying they are not directly related but they might use the same component. For example, I'm publishing a page in EN language but when I look at the dispatcher queue I can see pages from all the other languages being published. They don't use any XF or CF in common (some might but not all).

    It's happening on our DEV environment

    anupampat
    Community Advisor
    anupampatCommunity Advisor
    Community Advisor
    November 19, 2024

    Hi @fbfr ,

     

    Multiple things can trigger such behavior : 

    1. Any listener which listens to a page replication event and finds relevant pages and publishes them too.

    2. If you are on MSM, it could be a roll-out config which can trigger such behavior too. Although you should already see the relation between these pages.

    3. Any workflow which is triggered based on a launcher.

     

    Regards,

    Anupam Patra

      A_H_M_Imrul
      Community Advisor
      A_H_M_ImrulCommunity Advisor
      Community Advisor
      November 22, 2024

      Hello @fbfr,

      Hope you are doing fine.

      Few questions:

      - How are you publishing the pages (quick-publish, manage-publish or any custom workflow)?

      - Do you have any custom interceptor (like replication preprocessor, listener)?

      - How are you ensuring that additional pages are being published? I hope you checked the content being updated on publish.

      - Can you please check what workflow instances you see in the workflow dashboard?

       

      With the above detail we will able to investigate more..

       

      Thanks  

       

        F
        fbfrAuthor
        Level 2
        November 26, 2024

        Hi,
        - It's a quick publish

        - I'm not sure, we do have the replication-service being the one initiating the replications in the logs
        - I'm checking the agents.publish on the publisher instance and the logs. There's no content being updated as the pages weren't modified.

        - I don't see any workflows being activated as I publish the page, it seems to come from elsewhere

         

        Hope this helps investigate ! Thanks 

        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        November 25, 2024

        @fbfr Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

        Kautuk Sahni
        Terms & ConditionsAccessibility statement

        Loading footer...