We've confirmed that the issue with federation versions 2.9, 2.10, and 2.11 is resolved.

We've rolled back federation version 2.9 to its previous minor version, which should resolve the issue for that federation version. We're still working on confirming that the issue is completely resolved.

We've rolled back federation versions 2.10 and 2.11 to the previous minor version, which should resolve the issue for those federation versions. We're continuing to investigate potential issues with federation version 2.9.