No blocking replication even if we have one contribution issue

[#1]

Demande de résumé des améliorations des fonctionnalités (RFE) :	No blocking replication even if we have one contribution issue
Cas d’utilisation :	multiple times we were facing incident with blocked replication queue due to a contribution issue, it has not to arrive for a contribution issue !
Comportement actuel/expérimenté :	replication blocked for a single asset wrongly contributed
Comportement amélioré/attendu :	not block replication even if one asset is wrongly contributed, we can ignore it, and warn admin team that we have an issue on this one...and let replication continue for all the other data
Informations sur l’environnement (version d’AEM / service pack, et autres informations spécifiques si applicables) :	AEM Assets as Cloud Service
Nom du client/de l’organisation :	Louis Vuitton, Nathalie Riasse
Copie d’écran (si applicable) :
Package de code (si applicable) :

[#2]

@NathalieLV Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-17216. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.