Issue

Publishing concurrent content views (3-4 in parallel) frequently raises an error on the foreman smart proxy. The result is that the (composite) content view task is paused in error state and still keeps the locks on the content reserved. These locks of the paused task are then blocking any other publishing actions with (composite) content views.
With long running (15+ minutes) content view publishing actions, concurrent content view actions occur frequently. This happens especially often when composite content views (but also lifecycle promotions) are used, because when a product content is updated, also the composite content views (or the promoted versions) have to be updated and republished.