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

Timeout Handler not working in AEM 6.4.2

Avatar

Avatar
Ignite 1
Level 1
manishprabhut20
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
Give Back
View profile

Avatar
Ignite 1
Level 1
manishprabhut20
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
Give Back
View profile
manishprabhut20
Level 1

11-02-2020

We have a custom workflow for Activate Later in AEM 6.4.2 which is migrated from AEM 5.6.1 which have the below steps:

1. Create Version- The version is created succesfully

2. Participant Chooser Step: Wait for activation assigned to admin user and have the timeout settings value are as follows:

a. Timeout Handler: Absolute Time Auto Advancer

b. Timeout: Immediate

3. Activate

 

The workflow is stuck in step 2 and is throwing the below warning in the log-

-Granite Workflow Timeout Queue(com/adobe/granite/workflow/timeout/job)] com.adobe.granite.workflow.core.job.TimeoutHandler WorkItem does not exist: /var/workflow/instances/server0/2020-01-13

 

Even if the workitem node exists in the path mentioned.

We tried giving the permissions to workflow-service user and workflow-process-service user but the same error is coming.

 

Please provide some suggestions.

Replies

Avatar

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

511 likes

Total Posts

647 posts

Correct Reply

213 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

511 likes

Total Posts

647 posts

Correct Reply

213 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile
Vijayalakshmi_S
MVP

12-02-2020

HI,

 

The error says that process for "Timeout Handler"  does not exist.  Check for the status of the TimeoutHandler OSGI component in felix console. 

Also check if it is the case with new workflow as well.

  • Create a new sample workflow model in 6.4.2 instance
  • Configure participant/process step and hence define TimeoutHandler as "Absolute Time Auto Advancer".
  • Sync the changes and test the workflow.I

 

Avatar

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

511 likes

Total Posts

647 posts

Correct Reply

213 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

511 likes

Total Posts

647 posts

Correct Reply

213 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile
Vijayalakshmi_S
MVP

12-02-2020

Check the status of Absolute Time Auto Advancer as well (com.day.cq.workflow.timeout.autoadvance.AbsoluteTimeAutoAdvancer or com.adobe.granite.workflow.console.timeout.autoadvance.AbsoluteTimeAutoAdvancer) which ever you have associated. 

Avatar

Avatar
Ignite 1
Level 1
manishprabhut20
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
Give Back
View profile

Avatar
Ignite 1
Level 1
manishprabhut20
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
Give Back
View profile
manishprabhut20
Level 1

13-02-2020

Providing administrators group to the workflow-process-service and workflow-service resolved the same. If we happen to not provide to any one of the the above user it failed.