<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Error 429 on AI Lab @ Yuting</title><link>https://ailab.yuting.cc/tags/error-429/</link><description>Recent content in Error 429 on AI Lab @ Yuting</description><image><title>AI Lab @ Yuting</title><url>https://ailab.yuting.cc/images/ai-cover.png</url><link>https://ailab.yuting.cc/images/ai-cover.png</link></image><generator>Hugo</generator><language>zh-tw</language><lastBuildDate>Wed, 08 Jul 2026 16:51:26 +0800</lastBuildDate><atom:link href="https://ailab.yuting.cc/tags/error-429/index.xml" rel="self" type="application/rss+xml"/><item><title>揭密 Gemini 429 錯誤：動態共用配額 (DSQ) 下的容量策略與實踐</title><link>https://ailab.yuting.cc/posts/gemini-429-quota-management/</link><pubDate>Wed, 08 Jul 2026 16:51:26 +0800</pubDate><guid>https://ailab.yuting.cc/posts/gemini-429-quota-management/</guid><description>&lt;blockquote&gt;
&lt;p&gt;🔗 &lt;strong&gt;資料來源&lt;/strong&gt;：&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;此篇內容源自我們內部實戰解決 Gemini 429 錯誤的經驗總結。（&lt;a href="https://ailab.yuting.cc/downloads/Gemini-429-%E9%8C%AF%E8%AA%A4%E5%88%86%E6%9E%90%E8%88%87%E5%B0%8D%E7%AD%96.pdf"&gt;📥 下載原始簡報 PDF&lt;/a&gt;）&lt;/li&gt;
&lt;li&gt;延伸閱讀：&lt;a href="https://cloud.google.com/blog/products/ai-machine-learning/build-a-robust-and-cost-effective-gen-ai-strategy"&gt;Build a robust and cost-effective gen AI strategy (Google Cloud Blog)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;在大型語言模型的實際應用中，當我們以為配額相當充足時，卻時常會意外撞上 &lt;strong&gt;「429 RESOURCE_EXHAUSTED」&lt;/strong&gt; 的錯誤牆。本篇筆記將帶您深入剖析這個令人困惑的現象，並提供具體的架構調整與 Python 實踐範例。&lt;/p&gt;</description></item></channel></rss>