[MGNLWORKFLOW-133] workflow doesn't detect missing public instance or other failures in activation Created: 02/Sep/13  Updated: 01/Oct/13  Resolved: 01/Oct/13

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: 5.0
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Boris Kraft Assignee: Espen Jervidalo
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia EE 5.0.4


Issue Links:
duplicate
is duplicated by MGNLWORKFLOW-116 Fix exception handling in case or pro... Closed
supersession
is superseded by MGNLWORKFLOW-116 Fix exception handling in case or pro... Closed
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   

1. Assume you have no public instance, or it is not reachable.
2. Start a publication workflow, and then "accept & publish" it.
3. the activation will fail, with a message in the Pulse

However, now you cannot retry or do anything with the work item. Basically, workflow will tell you that the item is already taken care of (in which case by the way it should have removed the item from the Pulse, which it did not).

That is very confusing.

The way it should be: workflow should detect that the publication was not successful and keep the workitem around. It should also tell the user that there was a problem with activation; and allow her to try again.



 Comments   
Comment by Daniel Lipp [ 03/Sep/13 ]

This is actually a more general problem. Independently from the reason of the failure (missing public instance or whatever) the workItem has to stay in order to be able to retry.

Generated at Mon Feb 12 10:07:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.