Two people are reporting the same issue tonight; not reported previously despite same code for last month. Must be third-party change? Hmm.