Our latest production deployment on Vercel just failed with a build timeout error during the Next.js static generation phase, so how can I optimize the build cache?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Our latest production deployment on Vercel just failed with a build timeout error during the Next.js static generation phase, so how can I optimize the build cache?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
site:vercel.com/docs build cache Next.js .next/cache build timeout static generation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
site:nextjs.org/docs static generation generateStaticParams ISR build performance OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |