[MAGNOLIA-3812] Some items will disappear from inbox after 7 days Created: 26/Aug/11  Updated: 19/Dec/16  Resolved: 03/Nov/15

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 4.1.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Ondrej Chytil Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File magnolia-debug.log    
Issue Links:
supersession
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Steps to reproduce:

1.) Add at least 4 pages under website.
2.) Activate them taking note of the order they have been activated in.
3.) Check they all appear in the same order in the Inbox.
4.) Move the system (server) date less than 7 days ahead.
5.) Check all the workitems are still in the Inbox.
6.) Move the date 7 days or more ahead.
7.) Check the Inbox. Some of the items have disappeared.

In step 2, the order is of importance because most of the times the issue is reproduced the following observation is made:
If you number the items 1 to N being according the order they are activated into , after 7 days or more all items with odd numbers disappear and the ones with even numbers remain in the inbox.

When time is set back in testing items don't appear again.



 Comments   
Comment by Zdenek Skodik [ 20/Oct/11 ]

Personally I'm not so convinced that this is a bug. As far as my memory goes there is a default timeout set to 7 days and this default value you can override on the workflow definition level.

Comment by Ondrej Chytil [ 21/Oct/11 ]

Well as long this is happening only for half of workflow items it seems like a bug.

Comment by Zdenek Skodik [ 21/Oct/11 ]

Yes and no. There could be the bug in the timeout management, sure, but isn't here a bigger problem the disappearing itself?

When a item gets timed out (which may occur either when the work item is waiting to be started/served or even after it has been started ) the flow either continues to the next task or the timed out item is re-distributed to another group work list (both could stand behind the disappearing). This escalation needs to be explicitly specified through an if-than statement in the definition where the identity of the new resource allocated to the task is defined.

I see two possibilities:

  • define what should happen when timeout with use of on_timeout attribute
  • set the timeout to negative value (or no or none) to disable it at all (afaik this is the default value at ruby, the openwfe follower)

Some informations about this topic can be found in the openwfe manual (dms), other here (not sure how far it's supported by our current engine.

Comment by Michael Mühlebach [ 03/Nov/15 ]

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
Given that the this issue has seen no attention for quite a while and belongs to an outdated version, we're not going to address this issue any more. Instead we will focus on issues with a higher impact and more votes.
Under the assumption this issue is together with it's associated version no longer relevant, I'm going to close it to set expectations so the issue doesn't stay open for ages with no updates. If it is still relevant please feel free to open a new issue in the appropriate project.

Generated at Mon Feb 12 03:49:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.