restore All default workflow | Community
Skip to main content
lakshmi_raghava
lakshmi_raghava
Level 3
September 23, 2016

restore All default workflow

  • September 23, 2016
  • 4 replies
  • 6347 views

Hi All,

How to restore All default workflows in AEM 6.1 with SP2. Please provide the steps. we have taken the workflow as a package and install in instance which doesn't contains workflows. Once we installed that package, DAM update asset workflow is working fine for one image and from next upload image on words, workflow is going to stale mode, please provide the solution. 

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

4 replies

K
Adobe Employee
KanikaGeraAdobe Employee
Adobe Employee
September 23, 2016

You need to clarify the question. The /etc/workflow/launcher in CRX/DE has all launchers. Create a package and install it in the instance you need to restore froma fresh AEM instance. What does log say when it error out a workflow?

lakshmi_raghava
lakshmi_raghavaAuthor
Level 3
September 24, 2016

Hi,

Process execution result an error is the error that we are getting when workflow is going to stale mode. Please help me to resolve this.

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
September 24, 2016

Hi,

what is appearing in your error.log file? The problem may be in your content and not your workflow, you need to get to the cause of why your workflows are going stale.

Regards,

Opkar

lakshmi_raghava
lakshmi_raghavaAuthor
Level 3
September 24, 2016

Thanks Opkar for the update.

 

Following is the error that we are getting:

 

time=2016-09-23 19:49:07,946; thread=[JobHandler: /etc/workflow/instances/server1/2016-09-23/model_2469947358369859:/content/dam/ra/heroBanner/Rethinking Conventional Wisdom -Hero.jpg/jcr:content/renditions/original]; logger=c.d.c.w.c.CQWorkflowProcessRunner;  message=Process execution resulted in an error: null; tenantName=NA; userName=NA;

        at com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.execute(CQWorkflowProcessRunner.java:93)

        at com.adobe.granite.workflow.core.job.HandlerBase.executeProcess(HandlerBase.java:184)

        at com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:232)

time=2016-09-23 19:49:07,946; thread=[JobHandler: /etc/workflow/instances/server1/2016-09-23/model_2469947358369859:/content/dam/ra/heroBanner/Rethinking Conventional Wisdom -Hero.jpg/jcr:content/renditions/original]; logger=c.a.g.w.core.job.JobHandler;  message=Process execution resulted in an error; tenantName=NA; userName=NA;

com.adobe.granite.workflow.WorkflowException: Process execution resulted in an error

        at com.adobe.granite.workflow.core.job.HandlerBase.executeProcess(HandlerBase.java:194)

        at com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:232)

Caused by: com.adobe.granite.workflow.WorkflowException: Failed to execute process

        at com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.execute(CQWorkflowProcessRunner.java:108)

        at com.adobe.granite.workflow.core.job.HandlerBase.executeProcess(HandlerBase.java:184)

        at com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.execute(CQWorkflowProcessRunner.java:93)

 

 

and Problem is not with the content and same image we are uploading in our local and some other environments, Workflow is not going to stale mode. 

 

Please provide the solution else Please let me know, how to restore default workflow in AEM 6.1 with SP2.

lakshmi_raghava
lakshmi_raghavaAuthor
Level 3
September 24, 2016
        Mongo cluster instance.
O
Adobe Employee
ogillAdobe Employee
Adobe Employee
September 24, 2016

I have seen something similar before and it's not an issue with the workflow. You need to check the cluster topology, as this is used to distribute jobs in a cluster and if both of your author instances are not uniquely identified, then each author instance is behaving like a separate cluster, so each will try and run the workflow, which will cause your workflows to fail and go into a stale state.  The topology view should show all the instances in your cluster, if that is not the case you will have issues. Can you check all your instances to see how many nodes are present?

How many nodes do you have in your mongo cluster?

lakshmi_raghava
lakshmi_raghavaAuthor
Level 3
September 24, 2016
        If those instances are not unique,  is there any way to make those those unique,  suppose if I am copying the work flows from stand alone to Mongo cluster vice versa, how to resolve the issue. Same case from stand alone to stand alone,  how to resolve the issue.
O
Adobe Employee
ogillAdobe Employee
Adobe Employee
September 24, 2016

Hi,

It is the repository which needs to be unique, like I said it's nothing to do with the actual workflow, your repository is not configured properly.

I have seen this issue when customers have cloned/copied an instance to create a new instance in the mongo cluster, have you done this recently?

Is this your production system?

Have you checked http://<server name>:<port number>/system/console/status-topology How many nodes are present and how many nodes do you actually have in your mongo cluster?

Regards,

Opkar 

lakshmi_raghava
lakshmi_raghavaAuthor
Level 3
September 24, 2016

Yes Opkar, 

we recently copied the instance. I opened the topology. I am not able under stand anything. 

No it's not a production environment, it is our lower environments.

I attaching the those text file and please go through those and please let me know, if you know any solution. 

Terms & ConditionsAccessibility statement

Loading footer...