Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.
Improve Replication Queue not to block other queues when "Blocked Replication Queue" occurs
ユースケース：
When an error occurs in the replication queue and the queue is blocked, subsequent queues cannot be processed until the blocked queue is removed by someone. With this limitation, we'are facing a critical challenge in our operation such as; - when a block occurs on weekends or at midnight, there is no one who can remove the blocked queue, so any pages and/or assets cannot be published until next business day. - when a block occurs on a Brand A's site, that also blocks other replication queues for Brand B.
Can you please change the behavior? such as skip the error queue instead of blocking all queues after an error occurs?
現在／体験した動作：
When an error occurs in the replication queue and the queue is blocked, subsequent queues cannot be processed until the blocked queue is removed by someone. Notification is sent from Action Center, so that someone in administrator can notice. But when a block occurs on weekends or at midnight, there is no one who can remove the blocked queue, so any pages and/or assets cannot be published until next business day.
改善／期待される動作：
Want only the queue with the problem blocked and the other queues running.
This has been reported to the engineering under the internal reference SITES-22561. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira status.
