Unable to view workflows in Inbox on Author instance

[phall_hershey]

Every workflow that I create is not appearing under the inbox tab on Author.  I am a admin of our author instance and even if the ticket is not assigned to me, I can still see all tickets.  This issue just started a week ago, and not sure what to do.  The managed services team is not helping at all and the ticket is a P2 ticket that was created yesterday. 

Wondering if anyone can help me figure out why the workflows are not appearing under inbox. 

[AnkurAhlawat]

This is not a know issue, as you have suggested that this has started appearing from a week ago. It seems it is due to some custom code that has been pushed to production.Could you please let me know which aem version you are using and if possible could you please check if you have make any changes in default workflows, or any custom workflow process is committed as part of recent release.

[varunmitra]

It's not possible for us to identify the issue with the information that has been provided.

The best course of action would be to verify if there is any error in your log files. Workflow instances are retrieved with the help of a Query. If the query fails, a repository exception is thrown. I looked up the code for this and the error logs would definitely help in resolving this issue. 

Also, it is likely that one of the workflow instance node underneath /etc/workflow/instances might have been corrupted(missing essential properties etc) and it's because of this your query might be failing.

[MC_Stuff]

Hi phall,

     Make use of escalation path for unresponsive from support.   Regarding the issue 

• Is your notification count increasing at top right corner http://host:port/projects when you start a workflow?
  • If yes then issue with nodes or index.
    • Access http://host:port/libs/cq/workflow/content/inbox/list.json?_dc=1495663860715&start=0&limit=40 xero record means index issue. 
    • Not well formed json means issue at content. Delete the largest problamatic node from above output. 
  • If does not appear in notification means system is exhausted by other thread consuming the resource.   Need to identify & fix it. 

Thanks,

[phall_hershey · Accepted solution]

Worked with Adobe Daycare team to resolve the issue.

The issue was the result of the lucene index not starting.  After restarting our author instance, the lucene index started working.

Thanks to all that replied to my post.