Workflow Purge Config Not getting created on Higher Environments(dev server)

[kchaura]

Hi Everyone,

We are using AEM 6.5.21 service pack and I have set a environment specific configuration through my code base in osgi config folder using OOB workflow purge osgi service i.e Adobe Granite Workflow Purge Configuration, after deploying the code it gets created in local author and works fine but it is not getting created in higher environments(dev).This is only happening for Granite Workflow Purge Configuration and not for any other configs. Has anyone noticed this issue ? Thank you.

com.adobe.granite.workflow.purge.Scheduler-myproject-workflowPurgeTest.cfg.json

{
  "scheduledpurge.modelIds":[],
  "scheduledpurge.daysold": "90",
  "scheduledpurge.name" : "workflowPurgeTest",
  "scheduledpurge.workflowStatus": ["COMPLETED","FAILED"]
}

[Tethich]

Hi @kchaura 

I am sure you have config files in order, but just to be sure, how does your osgiconfig folder looks like ?

[kchaura]

@Tethich Thanks for the response. Yes it is the exact same order that you shared it is under osgiconfig/config. I do not see any issues with other configurations except workflow purge. seems it is taking precedence from /apps/system/config instead osgiconfig/config path from higher environments. 

[PRATHYUSHA_VP]

Hi @kchaura 

In that case, you have to remove the config from /apps/system/config in order to pick environment specific configuration 

Thanks

[kchaura]

@PRATHYUSHA_VP I have already done that but still no luck. Thanks

[Tethich]

You need to clear apps in order to avoid configs overlapping. Keep only one config for the workflow purge, the one from your codebase.

[kchaura]

I did not get exactly. Could you please explain ? I deleted all the config from dev environment created from system console and only deployed the config from the code . I see my config  under apps/config but the same is not being reflected in system console., thanks

[Tethich]

I meant exactly what you did.

• Are you sure the other configs get deployed or you have a false positive sentiment that they do. Maybe you can try modify something in another config file and see if it gets deployed. Or maybe you can try a deploy in local on a fresh new AEM instance and see if you can confirm the reported behavior.
• Also, worth checking the filter.xml, and see what do you have there.
• Check upper env error.log file for any xzibits. Especially look for any log message mentioning OsgiInstallerImpl.
• Check the same OsgiInstaller but now via the tool http://localhost:4502/system/console/osgi-installer

[kchaura]

Hi @Tethich Yes other configs are getting deployed there are no any issues apart from workflow purge config. I checked filter.xml  and other too config and looks good to me. Thanks