Dispatcher flush is not happening in aem cloud - never flushed | Community
Skip to main content
Mario248
Mario248
Level 7
September 27, 2024

Dispatcher flush is not happening in aem cloud - never flushed

  • September 27, 2024
  • 3 replies
  • 1455 views

After activating an AEM page in the author environment the page is published successfully in the publish environment. But the publish url is still being served from an old cache. I guess dispatcher cache is not cleared when the page is activated in AEM.

 

Disp Logs:

 

 

 

checking [/content/port/drum/masters/en/dbrand/test.html] cachefile does not exist: /mnt/var/www/html/content/port/drum/masters/en/dbrand/test.html try to create new cachefile: /mnt/var/www/html/content/port/drum/masters/en/dbrand/test.html cache-action for [/content/port/drum/masters/en/dbrand/test.html]: CREATE Filter rule entry /0010 allowed 'GET /content/port/drum/masters/en/dbrand/test.html HTTP/1.1' never flushed [/mnt/var/www/html/content/port/drum/masters/en/.stat] -> use cache [/mnt/var/www/html/content/port/drum/masters/en/dbrand/test.html] cache-action for [/content/port/drum/masters/en/dbrand/test.html]: DELIVER request declined

 

I have configured /statfileslevel "5", /allowAuthorized "0", and turned off /enableTTL "0".

Do you know why it shows "never flushed" at the 'en' level?

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

3 replies

h_kataria
Community Advisor
h_katariaCommunity Advisor
Community Advisor
September 27, 2024

Cross check your invalidate section as well https://experienceleague.adobe.com/en/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration#automatically-invalidating-cached-files and if it is AEMaaCS then take care of this https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/caching#cache-activation-deactivation 

    Mario248
    Mario248Author
    Level 7
    September 27, 2024

    I crossed checked the config and looks like everything is fine. any idea when do we get "never flushed" message in dispatcher 

      daniel-strmecki
      Community Advisor and Adobe Champion
      daniel-strmeckiCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      September 27, 2024

      Hi @mario248,

      I haven't seen this issue, but there must be something wrong in your Dispatcher config. I suggest that you test your Dispacher locally with SDK and default vs your config.

       

      Good luck,

      Daniel

        RiteshY18
        Community Advisor
        RiteshY18Community Advisor
        Community Advisor
        September 27, 2024

        @mario248 set statefileslevel to zero , it would delete entire cache from root , right now it is 5 causing /checking cache at level 5 and your page seems to be not at  level 5  

          Mario248
          Mario248Author
          Level 7
          September 30, 2024

          yeah, tried with statefileslevel 0, 1, and 2 but nothing happened.

            RiteshY18
            Community Advisor
            RiteshY18Community Advisor
            Community Advisor
            October 9, 2024

            you mean result is same as before when it was setup for 5 , What do you see on the console: success and error message?

            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            October 9, 2024

            @mario248 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...