Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Unable to view workflows in Inbox on Author instance

Avatar

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
phall_hershey
Level 2

23-05-2017

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. 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
phall_hershey
Level 2

05-07-2017

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.

Answers (3)

Answers (3)

Avatar

Avatar
Validate 1
Level 8
MC_Stuff
Level 8

Likes

78 likes

Total Posts

467 posts

Correct Reply

158 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 25
View profile

Avatar
Validate 1
Level 8
MC_Stuff
Level 8

Likes

78 likes

Total Posts

467 posts

Correct Reply

158 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 25
View profile
MC_Stuff
Level 8

24-05-2017

Hi phall,

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

Thanks,

Avatar

Avatar
Give Back 5
Level 2
varunmitra
Level 2

Likes

8 likes

Total Posts

31 posts

Correct Reply

4 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Boost 5
View profile

Avatar
Give Back 5
Level 2
varunmitra
Level 2

Likes

8 likes

Total Posts

31 posts

Correct Reply

4 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Boost 5
View profile
varunmitra
Level 2

24-05-2017

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.

Avatar

Avatar
Ignite 5
Level 6
AnkurAhlawat
Level 6

Likes

111 likes

Total Posts

165 posts

Correct Reply

27 solutions
Top badges earned
Ignite 5
Ignite 3
Ignite 20
Ignite 10
Ignite 1
View profile

Avatar
Ignite 5
Level 6
AnkurAhlawat
Level 6

Likes

111 likes

Total Posts

165 posts

Correct Reply

27 solutions
Top badges earned
Ignite 5
Ignite 3
Ignite 20
Ignite 10
Ignite 1
View profile
AnkurAhlawat
Level 6

24-05-2017

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.