Noted the same behavior on my end yesterday.
I think passing in the custom instructions manually in the message as before will likely be a workaround until the situation is fixed.
It’s not that I like it but it’s also something that can be dealt with in many cases.