[PUBLISHING-89] Incorrect Notification Is Displayed When Publishing Long-Running Actions Created: 23/Sep/20  Updated: 29/Mar/22  Resolved: 25/Mar/22

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Quach Hao Thien
Resolution: Won't Do Votes: 0
Labels: VN-Analysis, to-verify
Remaining Estimate: Not Specified
Time Spent: 1d 6.5h
Original Estimate: Not Specified

Issue Links:
causality
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:
Team: Nucleus

 Description   

A quick banner message appears when you try to "publish incl. subnodes" for a long-running process, but no notification appears in pulse. If you then try to "publish" a second content item, then you will receive a notification in pulse for both the current process and the first process saying that the first process is completed successfully, but in reality the first process is still running.

Steps
1- Go to the Assets App and create a folder that contains many images.
Example - What I did was duplicate many images such as those found within the "tours" folder, then created copies of the tours folder within another folder such that it would look like:
-somefolder
--> tours0
--> tours1
--> tours2
etc...
Where each folder has many images.

2- Click "Publish incl. subnodes" on the folder with the images
Example - I clicked "Publish incl. subnodes" for "somefolder"

3- You will see a brief notification saying: "The action will take a while to complete..." but no notification will show up in Pulse.

4- Click "publish" on some other content. (not necessarily a folder with a lot of images, it can be whatever, just one image)

5- You will see TWO success messages , 1 for the first action and one for the current publish action you just did. But the first action is still going so it is incorrect.

Expected
-You will see the correct message in pulse for the "long running action" notification once it gets triggered.
-The notification won't say it ran successfully when it is actually still running and it is not completed.
-The second process should not trigger the first process's notification

Actual 
-You do not see any "long running action" notification in pulse.
-Notification will incorrectly say the process finished, when it really did not
-The second process triggered the first process's notification.

Additional Notes
Publication does not seem to be affected, the issue is more with the notifications and their timing and message.



 Comments   
Comment by Quach Hao Thien [ 07/Mar/22 ]

Discovery completed

Tested on 6.2.18

  • You do not see any "long running action" notification in pulse. << "Long running action" is showing via notification popup, not via Notification app
  • Notification will incorrectly say the process finished, when it really did not << Notification (via Notifications app) shows correctly when process finished.
  • The second process triggered the first process's notification. << Notification for single Publish (NOT Publish incl. subnode) doesn't trigger any notification, even via popup or app  MGNLUI-5391
Comment by Rabie Hayoun [ 25/Mar/22 ]

Cannot be reproduced on 6.2.18, dropped for low support score and long time inactivity.

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