Activate Later triggers workflow which requires admin approval...?? CQ5.5

I believe you are talking about 'Request for Activation' workflow - what you are calling as issue is the expected functionality as there are two steps in workflow -

1) Approve content
2) Request for activation

Both these steps require approval, thus your workflow keeps on waiting probably at the second step. What you can do it approve both the steps and let the workflow wait for its scheduled time to get executed or you can remove the second approval step in case you dont require two step approval in any of your publishing scenarios.

There is an example workflow - 'Publish Example' which has the just one level of approval required, try scheduling your content activation using this workflow and it should work with single level of approval.

Thanks
Ameesh
 

Hi Yogesh,

Thanks for the reply but we have already checked that the user has proper permissions and also since we are able to manually complete the workflow I understand it's not the issue with permissions.Also, this issue is only occuring on one of our environments. Please let me know which eventing bundle could cause this issue.

Thanks,

Alka

Hi Ameesh,

Thanks for the reply but when you use activate later it uses Scheduled Page/Asset Activation wrokflow and not the request for Activation workflow and in case of Scheduled Page/Asset activation approval is not required.Correct my understanding.

Thanks,

Alka

Can you provide snapshot of the workflow and the step Waiting for activation covering details of timeout settings.

Hi Ameesh,

Attached snapshot of the workflow model and workflow waiting for approval step.

Thanks,

Alka

Logs from the production env, where this error is happening:

[JobHandler: /etc/workflow/instances/2013-12-02/model_474611178883249:/content/mohegansun/en/GenericContentTest] com.day.cq.workflow.impl.job.JobHandler Start processing: /etc/workflow/instances/2013-12-02/model_474611178883249:/content/mohegansun/en/GenericContentTest

02.12.2013 06:07:55.904 *INFO* [JobHandler: /etc/workflow/instances/2013-12-02/model_474611178883249:/content/mohegansun/en/GenericContentTest] org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceManager cachename=crx.defaultBundleCache[ConcurrentCache@70849e34], elements=1773, usedmemorykb=8188, maxmemorykb=8192, access=71687690, miss=10665899
02.12.2013 06:07:56.471 *INFO* [JobHandler: /etc/workflow/instances/2013-12-02/model_474611178883249:/content/mohegansun/en/GenericContentTest] com.day.cq.wcm.core.impl.PageManagerImpl Created new version 1.1 for /content/mohegansun/en/GenericContentTest
02.12.2013 06:07:56.488 *INFO* [JobHandler: /etc/workflow/instances/2013-12-02/model_474611178883249:/content/mohegansun/en/GenericContentTest] com.day.cq.workflow.impl.CQWorkflowSession Attempting to complete work item with ID: VolatileWorkItem_node4_etc_workflow_instances_2013-12-02_model_474611178883249
02.12.2013 06:07:56.541 *INFO* [JobHandler: /etc/workflow/instances/2013-12-02/model_474611178883249:/content/mohegansun/en/GenericContentTest] com.day.cq.workflow.impl.job.JobHandler Finished processing: /etc/workflow/instances/2013-12-02/model_474611178883249:/content/mohegansun/en/GenericContentTest(Complete execution took: 989ms)

it seems that Item gets moved to inbox once workflow is activated but the job for activating it at the schedule time is not working. In another environment where activate later is working fine I see following logs after the above:

02.12.2013 06:34:00.258 *INFO* [pool-6-thread-18-<main queue>(com/day/cq/workflow/timeout/job)] com.day.cq.workflow.impl.CQWorkflowSession Attempting to complete work item with ID: /etc/workflow/instances/2013-12-02/model_24454178823561983/workItems/node1_etc_workflow_instances_2013-12-02_model_24454178823561983

Can anyone suggest where can I check that the work items/threads are getting created for the workflows? 

Any pointers would be helpful.

Regards,

Alka

can you disable versioning and see if it works. If so please file daycare & request for a hotfix. 

Its production server, i cannot disable versioning on it. Not able to replicate the same on my local.

If you can;t reproduce. I would say restore the production copy into local instance & try it out.