Adobe cq5 workflow issue | Community
Skip to main content
K
kishored6899358
Level 3
September 6, 2017
Solved

Adobe cq5 workflow issue

  • September 6, 2017
  • 6 replies
  • 2485 views

Hi,

We are using aem 5.6.1 in our project. We ran a workflow on a page but it went in 'Stale' state. We tried to terminate from workflow console but no luck. So we had deleted the corresponding workflow instance from etc/workflows.

We have another issue now. When we tried to run a workflow on that page, it was saying like 'The page is already subject to a workflow'. We checked the workflow console no workflow exists in any state for that page. The workflow tab in sidekick is blank.

Can anyone please help?

Regards,

Kishore

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 viveksachdeva

I am not very sure but it seems that the info is picked from AEM cache.. Restarting the instance should fix it..

6 replies

viveksachdeva
Community Advisor
viveksachdevaCommunity AdvisorAccepted solution
Community Advisor
September 6, 2017

I am not very sure but it seems that the info is picked from AEM cache.. Restarting the instance should fix it..

K
kishored6899358Author
Level 3
September 6, 2017

Thanks Vivek for the suggestion. But I am looking for any oher way to resovle this issue. We will consider restarting AEM as a last option.

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
September 6, 2017

Sad to say, but this is a common problem with older versions of AEM/CQ5. A lot of these problems have been fixed with later versions.

I would recommend to upgrade to a later versions (which is anyway a good idea, as this version already ran out of general support).

Jörg

K
kishored6899358Author
Level 3
September 7, 2017

I agree. No clue found from the logs related to the issue. So we thought of giving try to restart AEM. Fortunately that fixed the issue.

Thanks everyone for providing suggestions.

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
September 7, 2017

If a restart of the instance fixes the problem, you can also try to restart the "Sling Event Support" bundle instead.

Jörg

K
kishored6899358Author
Level 3
September 8, 2017

Thank you Jörg, we will try this out when we come across such situation in future.

Terms & ConditionsAccessibility statement

Loading footer...