8 months of due diligence of making X-Total-Count lowercase internally at SailPoint and it was not realized that the workflows still had it in uppercase, after which it got quickly changed to lowercase without realizing that this would break customers processes in production.
@Takato, this would be another case that showcases the feedback I gave when you were looking into workflow versioning: that the focus should not only be on ensuring that customers can change their workflow configuration and still have previous configurations available in case of rollbacks being required, but that whenever SailPoint makes changes to behavior of workflows, they need to have versioning. This way you could say: "all (current) workflows still use version X, where X-Total-Count is used, but please upgrade to version Y within 3 years, where x-total-count is used. This way you can both facilitate progress and ensure that old workflows keep working.
In a similar way, introducing breaking changes (which this is regardless of the workflow change), if unavoidable, should be communicated using more channels (e.g. ensuring CSMs inform their customers, a popup when logging into ISC, etc.) and if possible, more in advance.