When a concurrent cycle fails, Shenandoah still updates the heap usage metrics. At the point of failure, the heap usage is generally close to 100% and does not accurately reflect the amount of live data on the heap.