Workflow model is not refreshed. Old version is used | Community
Skip to main content
M
Marek_Krokosins
Level 2
March 31, 2018

Workflow model is not refreshed. Old version is used

  • March 31, 2018
  • 2 replies
  • 4212 views

So I have a workflow model, which is used in one scenario. I have several environments. On the fresh environment my workflow model works as expected.

On existing environments it seems that it uses old version of the workflow. I would like to ask if workflow model are cached somewhere ? If yes, how can I purge the cache ?

If workflow models are not cached, what can be cause of such issue? In logs I get information that "No route found to continue from step node5". I'm sure that workflow model is correctly configured, because it works on new environment, so that's definietely something on AEM side. I can see in CRX that workflow is installed, I tried to save it again in the workflow model editor, but that didn't help. It fails on my second or split, It reaches or split and then it says that it cannot proceed to next step. Do you have any idea what can be wrong ?

I have tried to remove all instances of running and completed workflow model thorugh maintanance task, then I have removed workflow completely. I have reinstalled it through package but still I had the same issue. Of course restart of AEM instance also doesn't work.

I'm using AEM 6.3 SP1 (author)

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

    2 replies

    smacdonald2008
    smacdonald2008
    Level 10
    March 31, 2018

    This sounds strange - if you have the exact workflow as you have on your fresh environment - you should be getting the same results. So the community better understands - can you please post a screenshot of your model.

    M
    Marek_KrokosinsAuthor
    Level 2
    March 31, 2018

    that is not possible. Simple or split with default steps and two branches.

    What I can add, is that I'm editing default Request for Deletion workflow.

    smacdonald2008
    smacdonald2008
    Level 10
    April 1, 2018

    I have asked the AEM workflow Eng team to look here. If the workflow works on 1 instance and if you setup the same workflow and all the dependencies properly - it should behave the same way.

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    April 2, 2018

    Which version are you on?

    Nothing that we can find out with latest AEM version.

    Request you to create a Support ticket for this.

    -Kautuk

    Kautuk Sahni
    smacdonald2008
    smacdonald2008
    Level 10
    April 2, 2018

    Support stated:

    It could be two reasons.

    1. Force class re-compile
    2. Run offline compaction.

    If those above does not work, have them to log the case.

    crisr1
    crisr1
    Level 4
    July 25, 2018

    I have solved this.

    It super weird, but I have no time for debugging it right now.

    So thing which fixed problem for me:

    In Or Split I was using script file. In each branch.

    I have removed path to the script and I made copy-paste of the script content into the text area of each script.

    Because of some freaking reason, it has fixed the problem.

    I have other custom workflow (the one with which I had problems was default delete workflow) which were using script files, and they seem to work properly, even though they are configured to use script from the file.

    I have not change even a line of the script, and that is something which surprises me very much. It fixes the problem on all environments where it was designed.

    Additionally, I noticed that I didn't have CFP2 installed locally on fresh environment, after installing it, workflow stopped working, and I had to apply fix which I described above. Maybe CFP2 introduced a new bug.


    Thanks for posting about this problem. We are also facing this issue with workitems not having the routes object when preceding an OR Split. Actually pasting the script into the OR Split branch text editor did help in our case! but it needed to be added into the non default branch.

    Terms & ConditionsAccessibility statement

    Loading footer...