The root cause was identified as a bug that surfaced during routine maintenance operations. The issue has been resolved permanently with a code deployment.