Escalations

STARK-44 enterprise checkout is 500ing because calculate_total calls validate_quantity on an item with quantity=None, which raises ValueError and bubbles up as a 500 right after the recent deploy window.

Enterprise checkout for STARK-44 is 500ing because the checkout payload has items with missing quantity (None), which trips validate_quantity and bubbles as a server error.

STARK-44 (enterprise) is seeing checkout 500s that align with a recent bindu-bazaar production deploy; the checkout code strictly validates item quantity, and missing/null quantities would trigger failures for this account only.

Checkout failures for STARK-44’s enterprise team align with a misconfiguration: the enterprise-only customer_org claim on their account is not configured, while other core claims are enabled; prior orders for this account did succeed, suggesting a recent regression surfaced this gap.

STARK-44 (enterprise) is failing checkout likely because a recent production deploy started enforcing a customer_org claim that this account does not have configured.

STARK-44’s enterprise checkout 500s likely started after today’s production deploys began enforcing a customer_org claim that this account doesn’t have configured.

For STARK-44, checkout and order placement succeeded during the reported window with no 5xx observed; only notable config is the enterprise claim 'customer_org' set to not_configured.

Insufficient signal to classify; requesting more information from the reporter.

Insufficient signal to classify; requesting more information from the reporter.

Insufficient signal to classify; requesting more information from the reporter.