Thanks a lot @Jörg_Hoh , and please do not apologize, it is a needle in a haystack. Please do provide me with the url of the post you update and i will keep it for reference.Quick question - If i do this , which is closing it, will it hamper next steps in the workflow by any chance ?try(ResourceReso...

yes, reason i confirmed is, strangely, when i tried adding the autocloseable try and the info message for the custom class disappeared. The blogs however, unless i am missing something do not speak to workflow session . I see it implemented with autocloseable try to close the session/resolver in ACS...

Agreed and hence the confusion .. Using closeable try means we are closing it .. right @DEBAL_DAS ?  try(ResourceResolver resResolver = workflowSession.adaptTo(ResourceResolver.class))    

Thanks Kiran, i totally agree.,..but i see nothing else causing it. How would you identify? below are the logs. I am on 6.5.12 and before this i see bunch of unclosed resolvers in ootb codeBtw, my step is after the "metadata processor" in the OOTB update asset workflow   org.apache.sling.resourcere...

Hi @Kiran_Vedantam  i am not sure I follow . I have obtained it from workflow session via adaptTo and hence I don’t believe I should close it or use the autoclosable try block. I don’t want to close the resolver and create an issue with the resolver being closed for next steps within workflow  pleas...

Hi @Anudeep_Garnepudi not sure what you mean but I know it is not the wrong way to get the resolver . Question becomes, should I close it ? Which I believe should be a no , since u have not opened it .hence I believe no need for an auto close able try block  i do not want to get the resolver via ser...

All, I have a custom process step within the dam update asset workflow where the step needs a resource resolver instance which I get from the workflow session via adaptToResourceResolver resResolver = workflowSession.adaptTo(ResourceResolver.class);I do NOT have a closeable try block as in below sin...

Anyone facing the issue ,received confirmation from adobe ..  this is a bug and that has been existing with tagid and the KB still holds good since the issue exists since I guess 2017  ignoring the info messages is the suggestion.    https://helpx.adobe.com/au/experience-manager/kb/Unclosed-Resource...

Anyone facing the issue ,received confirmation from adobe ..  this is a bug and that has been existing with tagid and the KB still holds good since the issue exists since I guess 2017  ignoring the info messages is the suggestion.    https://helpx.adobe.com/au/experience-manager/kb/Unclosed-Resource...

Anyone knows about this ?