[patio11]

I work at Stripe and happened to see this thread a few minutes after we had started an incident response to resolve the underlying bug.

So, long story short: We did a deploy yesterday for a thing which is not obviously related to the Dashboard's product SKU editing screen. There was an unplanned interaction between some work done for that deploy and the Dashboard product SKU editing interface; this resulted in some users having partially degraded HTML shipped to them (without the fields for editing SKU inventory quantity and SKU active/inactive status).

After we became aware that this happened due to Dan's comments, we opened an incident, diagnosed the regression, put a temporary fix in place, and started working on a more permanent fix.

I'm sorry we dropped the ball with respect to the support inquiry about this; our representative came to the conclusion that this was a planned change in functionality, even though this particular interaction was not planned. We'll look into how that happened and correct it.

[sching]

I also work at Stripe and have been working on remediating these Dashboard workflow issues. We've pushed comprehensive fixes for the regressions. I'm also looking into our support representative's initial misunderstanding of the issue. I appreciate the flag here and would encourage anyone to get in touch with us directly via https://support.stripe.com/ with questions if they notice any unexpected behavior post-fix.

[dan_m2k]

As to your colleague, thank you. If I can be of any help in helping identify where support went wrong, please hit me up.