Well just a follow-up. Much as I didn't want to because the impact on production systems, the only way to resolve this "bug" was to reinitialize the entire subscription.

After...