Check out .. https://docs.adobe.com/docs/en/dispatcher/disp-config.html#Automatically Invalidating Cached Files  -- This should solve your problem. With your deny all, you're effectively doing resource-only flushing for everything.

What's the stat level and and invalidate config I your dispatcher.any?

sanjays16398239​ It would be helpful if you could provide your log for the invoked flush agent and the dispatcher log (on debug) that shows how dispatcher is processing the flush and finally, the dispatcher log for when you request a page that you now expect to be invalidated.

Double-check your POMs (Parent AND bundle/core) to make sure you are using the proper uberjar and NOT directly specifying the dependency version for:<dependency><groupId>org.apache.sling</groupId><artifactId>org.apache.sling.api</artifactId><version>x.x.x</version><scope>provided</scope></dependency...

SushantRao,ACS Commons Error Page Handler works fine for POSTs as well. If an error occurs, Sling handles the error and passes it off to the ACS Commons Error Page handle, which in turn internally makes a HTTP GET request for the error page defined by the @errorPages property.The problem your runnin...

1) Are these existing assets youre re-processing (they've been through DAM Update Asset once before)?2) If you do not need to extract sub assets at all, you can remove the "Create Sub asset" step from your DAM Update Asset Workflow Model (or create a copy and remove the step, and run that via BWM)Al...

Can you use Acs tools jsp code display [1] to report the line in the compiled JSP that is throwing the error?What version of Aem are you using, and have you changed the 404.jsp overlay at all? (Outside of how the acs commons docs recommend)Also if you can report this to the acs commons GitHub issues...