Stock History
Grow a Garden Stock History
Stock history helps players understand what appeared before, when it appeared, and how recently rare Grow a Garden seeds were seen.
How Stock Snapshots Work
The backend updater checks the public seed restock API on a short interval and stores only fresh stock windows in Supabase. This avoids saving the same response again and again.
Each stored snapshot keeps the source, stock window, fetch time, payload, and in-stock count so the site can build a reliable last-seen view.
Why Last-Seen Tracking Matters
A rare seed may be out of stock right now, but its last-seen time still gives players useful context. If an item appeared recently, it may be easier to understand the current rotation pattern.
Last-seen tracking is not a guarantee. It is historical context based on stored data.
Fresh Data Without Overloading APIs
The zero-cost architecture is designed to fetch once from the upstream API, store the result, and let the website read from Supabase instead of making every visitor hit the external source.
This is better for performance, more stable for visitors, and safer for the public API.
Frequently Asked Questions
Does GAG2 UNLOCKED store every duplicate API response?
No. The updater is designed to store fresh stock windows and skip repeated stock windows that have already been saved.
Can history be wrong?
History depends on successful API calls and stored snapshots. If the upstream API is blocked or unavailable during a window, that window may be missing.