This sounds like it could be the same issue we’re experiencing in other places.
See my latest comment on this other post where I discuss what I’ve found so far:
Another related issue that I’m having, apparently due to the same bug: