brp
TUG Member
Thanks for sharing. Perhaps the delay is due to a reduced IT staff.
Problem is, AFAIK, this had been working previously. So it would appear that they did something to cause this rather than just not having staff to fix an extant issue. This is one of their somewhat common problems: rolling out new features without proper testing. If they are short-staffed, best approach is th delay rollout and allow the additional testing time required with reduces resources.
If customers are demanding certain new features, that's one thing. These don't seem to be things that we demanded. Rather things that they unwisely rushed out without proper regression.
Cheers.