[MGNLDAM-441] (Potentially) long running actions should be configured to run asynchronously Created: 07/May/14  Updated: 03/Jun/14  Resolved: 21/May/14

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.5

Type: Improvement Priority: Critical
Reporter: Daniel Lipp Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLUI-2840 (Potentially) long running actions sh... Closed
is cloned by MGNLDAM-462 (Potentially) long running actions sh... Closed
relation
is related to MGNLUI-2783 User is blocked in his browser sessio... 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)
Date of First Response:

 Description   

With MGNLUI-2783 we introduced a way to run commands asynchronously. This should now be applied (on fresh installations as well as on updated ones) to:

  • recursive publication
  • deletion

as both of the actions involve versioning of content and can be time consuming



 Comments   
Comment by Jaroslav Simak [ 21/May/14 ]

Reopened:

  • Update tasks should check if scheduler is registered/installed and if so, then it should enable async actions (if scheduler is not installed, it will break activation/deletion)
Generated at Mon Feb 12 04:59:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.