Activate Later Workflow Fails at Activate Page / Asset step | Community
Skip to main content
New Participant
February 4, 2016
Solved

Activate Later Workflow Fails at Activate Page / Asset step

  • February 4, 2016
  • 1 reply
  • 837 views

The environment has several publish agents on Author (10 or more) of which only one is enabled.  The others point to publish instances which are not running.

Basically, activating content works as expected, the content is published.  However, when the “activate later” option is selected, when the workflow reaches the activate date the activate content step in the workflow seems to fail with “Job contains agent which is not started” errors.  Sometimes more than one error shows.

18.01.2016 14:20:01.237 *ERROR* [pool-7-thread-16-com_day_cq_replication_job_flush(com/day/cq/replication/job/flush)] com.day.cq.replication.impl.AgentManagerImpl Job contains agent which is not started: flush. 18.01.2016 14:20:01.237 *ERROR* [pool-7-thread-11-com_day_cq_replication_job_publish11111(com/day/cq/replication/job/publish11111)] com.day.cq.replication.impl.AgentManagerImpl Job contains agent which is not started: publish11111.

There does not seem to be a clear difference between the activate page/asset step of the two workflows. 

The "publish11111" is Publish agent 6 and it is one of the ones that is disabled.

Any direction would be appreciated.

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

For what it's worth....

Adobe provided a hotfix for this:  CQ-6.0.0-HOTFIX-7237

https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/packages/cq600/hotfix/cq-6.0.0-hotfix-7237 

1 reply

Rob_Curran__T4GAuthorAccepted solution
New Participant
March 4, 2016