Workflow Model is not updating on change | Community
Skip to main content
Level 2
July 3, 2025
Solved

Workflow Model is not updating on change

  • July 3, 2025
  • 3 replies
  • 572 views

Hi There,

 

I have developed custom workflow and installed it and it worked fine. I synced workflow model xml into codebase, made some changes (removed some steps and transition etc) and pushed it to AEM CaaS. But to surprise, AEM workflow is still using old workflow xml instead of using new one. Just FYI, I did not just update it manually but via local SDK and synced the code back. It changed `lastModified` and other properties as well, so it should recognize it as changed on deployment but it did not. On `/var/workflow/models` it still shows old nodes and transitions 

Best answer by aanchal-sikka

@bagwanpankaj 

Please assure that you have synced following to your codebase:

  •  /conf/global/settings/workflow/models/your-wf
  • /var/workflow/models/your-wf

 

Verify filter.xml. It should be set to replace for both of these paths

 

Couple of things:

  • The already running workflow instances would not pick the new workflow. You would need to initiate it on a different asset/page to test the latest changes.
  • Assure that the asset/page you are using doesn't have an old wf instance in execution. 

 

3 replies

SantoshSai
Community Advisor
Community Advisor
July 3, 2025

Hi @bagwanpankaj,

Ideally, The source of truth is in /conf/..., usually version-controlled and deployed via code. When you deploy a workflow model XML (e.g. under /conf/global/settings/workflow/models/xyz), AEM doesn’t automatically re-sync that to /var/workflow/models unless the model is either:

  • Modified through the UI

  • Programmatically re-synced

  • Explicitly deleted from /var before deployment (not ideal)

Santosh Sai
aanchal-sikka
Community Advisor
aanchal-sikkaCommunity AdvisorAccepted solution
Community Advisor
July 4, 2025

@bagwanpankaj 

Please assure that you have synced following to your codebase:

  •  /conf/global/settings/workflow/models/your-wf
  • /var/workflow/models/your-wf

 

Verify filter.xml. It should be set to replace for both of these paths

 

Couple of things:

  • The already running workflow instances would not pick the new workflow. You would need to initiate it on a different asset/page to test the latest changes.
  • Assure that the asset/page you are using doesn't have an old wf instance in execution. 

 

Aanchal Sikka
kautuk_sahni
Community Manager
Community Manager
July 11, 2025

@bagwanpankaj Did you find the suggestions helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you !

Kautuk Sahni