Fozzels October 2026: Image Flow limits and chunking Bubble bulk catalogs via BIAIG
Operational checklist for when Run Now eats Fozzels daily quota, Bubble bulk tools cap out at a few hundred rows, and model pricing news does not fix throughput.
Why ops limits beat model choice this week
October 2026 hit me with two kinds of news at once: Fozzels Image Flow operations changed in the same cycle as OpenAI Batch pricing (~50% vs sync) and Gemini image deprecations (nano-banana-2.1 GA; gemini-3.1-flash-image deprecated). Production stalled on the minimum of independent caps—per-flow daily processing, account completions/credits, Bubble scheduling and capacity—not on which image API is cheapest. Worth reading next: GPT Image 2.5 at 250.
This is Bubble-developer methodology, not a documented Fozzels↔Bubble product integration. BIAIG here is my in-house name for Bubble-side bulk catalog orchestration (chunk + Schedule API workflow on a list). Scout found no public canonical definition—I name the pipeline and write a runbook; you should too. Worth reading next: Fragmented bulk-tools niche: Apify spreadsheet.
Fozzels facts (vendor docs)
October 2026 Image Flow change
- Run Now now counts toward each flow’s configured daily products-per-day limit. At cap, the UI warns to raise the Automation limit or wait.
- Preview/test generations in preview are excluded from that limit.
Daily automation behavior (Image Flow user guide)
- Amount of images to process per day sets the daily budget.
- Plan & Close starts after the next nightly catalog sync pool.
- Run Now consumes the current day’s quota (post-October 2026 this matters when I push manually).
- One AI generation per product per flow; further attempts for the same SKU in that flow are skipped.
- I track work in Batch List; store sync after review remains manual.
The “500” number
- Content Flow docs state up to 500 products per active flow per 24-hour cycle.
- Image Flow uses the same Automation pattern and daily-limit field; on Image Flow pages in the Scout packet, “500” is not restated numerically—I plan conservatively until plan/support confirms parity for my account.
Account quotas (separate lever)
- Completions per day/month and credits can block generation even when the flow daily cap is not exhausted (Dashboard Overview and Account Usage Limits).
Bubble: “few hundred” vs 50k/100k
| Tool | Official guidance | Catalog implication |
|---|---|---|
| Make changes to a list of things | Intended for a few hundred records | Do not drive 5k–50k SKUs in one bulk action |
| Schedule API workflow on a list | 50,000 (sorted) / 100,000 (unsorted); excess not scheduled | Multiple invocations or recursive chunking |
| CSV upload | Plan-tier row caps (forum: 1k–30k)—not the same as SAWOL | Do not conflate with Fozzels daily flow cap |
Scheduling note: optional interval does not guarantee non-overlap on long lists; capacity limits can queue workflows—wall-clock time can stretch past Fozzels’ nightly cadence.
Sorted-list trap: I chunk with sorted searches above 50k and Bubble silently truncates scheduling—I validate counts in BIAIG logs.
Operational checklist
1. Stack the limits (take the minimum)
- Per-flow daily products (Run Now included since Oct 2026).
- Fozzels completions + credits.
- Bubble chunk size + capacity queue.
- Model IDs (migrate off deprecated gemini-3.1-flash-image toward gemini-nano-banana-2.1; Imagen 4 GA shutdown was 2026-08-17 per Google deprecations).
2. Run Now discipline
- I use Run Now only when I mean to spend today’s quota.
- Preview is for prompt/model QA—it does not count toward daily limit after the October release.
3. BIAIG-style chunking in Bubble
- I keep Make changes to a list batches in the low hundreds (practical default ~200–300—not a Fozzels-published constant).
- For larger sets, Schedule API workflow on a list with a logged chunk id (date, flow id, index).
- Fozzels allows one generation per product per flow; I avoid duplicate Bubble queue rows.
- I watch manual review backlog—throughput without reviewers is a false win.
4. OpenAI Batch is a different lane
- Up to 50,000 requests per batch file, ~24h completion target, 50% cost vs sync, image endpoints supported.
- Fozzels Image Flow is same-day interactive (Run Now, Batch List, manual sync). Batch API does not slot in without a separate import/reconcile design—I do not sell “Batch discount” as Image Flow savings until that path exists.
5. Launch day
- Flow daily limit × number of flows vs SKU count.
- Dashboard completions/credits.
- Live model strings vs Gemini changelog/deprecations.
- Bubble sorted vs unsorted SAWOL; per-invocation item cap.
- Owner for manual sync after batch review.
Honest unknowns
- Whether Image Flow shares the 500/day ceiling with Content Flow is not fully restated on all Image Flow docs—I verify for my account.
- BIAIG is editorial/internal naming unless my team publishes a glossary.
- Linking Fozzels SaaS limits, Bubble SAWOL, and OpenAI Batch is architecture inference, not one supported workflow.