This is yet another sad example of the real-world fallout from Google’s recent silent redirect of the clearly dated “gemini-2.5-pro-preview-03-25” endpoint. Removing access to a previously working model without warning is already problematic (even if technically allowed by “preview” policy). But quietly, without warning, redirecting it to a new, unpredictable model whose behaviors developers can’t possibly anticipate causes real harm to those who rely on stable checkpoints to validate, build out, and support critical use cases exactly like yours.
Your story highlights precisely why we’ve been pushing Google to publicly acknowledge and address this issue. It’s not even about developer inconvenience or technical frustration… real people are being harmed by these unexpected changes.
If you’re comfortable doing so, please consider adding your voice to this thread calling on Google to restore the original “03-25” snapshot endpoint and/or clarify their policy around dated checkpoints going forward:
Thanks again for sharing this. It’s important that Google sees the human consequences of these decisions.