Acs-commons dispatcher flush not working with Delete option | Community
Skip to main content
DPrakashRaj
Community Advisor
Community Advisor
August 22, 2023
Solved

Acs-commons dispatcher flush not working with Delete option

  • August 22, 2023
  • 1 reply
  • 807 views

Hi,

I recently upgraded the acs-commons version on ams and aem on-prem and notice that dispatcher flush for acs-commons only works for invalidate and not the delete option for content pages available for the configuration, if you have locked pages on aem for requested content node.

no issue with deleting clientlibs through acs-commons

it always throwing the error page locked unable to replicate.

Acs-commons version 6.0.14

aem 6.5.17

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

@dprakashraj This requires some debugging, but on my first guess, it could be due to some issue at the ACS level. Check this post: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/acs-common-dispatcher-flush-agent-not-working/td-p/390864#:~:text=If%20it%20doesn't%20work,have%20been%20fixed%20in%20those 

// Try using one of the latest versions of ACS Commons. The issue might have been fixed in those.

 

Worth checking this request: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues 

 

Related open Dispatcher issues already open: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues?q=is%3Aissue+is%3Aopen+dispatcher 

1 reply

kautuk_sahni
Community Manager
kautuk_sahniCommunity ManagerAccepted solution
Community Manager
August 28, 2023

@dprakashraj This requires some debugging, but on my first guess, it could be due to some issue at the ACS level. Check this post: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/acs-common-dispatcher-flush-agent-not-working/td-p/390864#:~:text=If%20it%20doesn't%20work,have%20been%20fixed%20in%20those 

// Try using one of the latest versions of ACS Commons. The issue might have been fixed in those.

 

Worth checking this request: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues 

 

Related open Dispatcher issues already open: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues?q=is%3Aissue+is%3Aopen+dispatcher 

Kautuk Sahni