Hey,
Thanks for following up here.
Even thougt the thread is closed, we will still reach out on the thread as our team makes progress on the issue. I took a look at our internal ticket for tracking this issue and unfortunately it doesn’t look like it was scheduled for this previously maintenance release, however it will be reviewed for inclusion in an upcoming release.
I apologize again for the continued inconvenience of this issue. If you have any further questions or concerns about this process, please don’t hesitate to reach out.
Thanks!