A bad change shipped in one API route. Rolling back the whole deployment also reverts unrelated fixes. Can I roll back a single function?

  • Theo Lindqvist Not today — deployments are atomic, which is what makes instant rollback safe. The usual approach is a revert commit for that route; with r…

All my routes respect s-maxage=300 except /products/[slug], which always shows x-drift-cache: MISS. Same handler code. What can make a single route uncacheable?

  • kwame.dev Does that route read cookies or headers? Any dynamic API call opts the whole route out of the cache.
  • marcobuilds It reads a currency cookie... that would do it. Moving that to the client.

Anyone with a preview URL can open it. We share previews with clients and do not want them indexed or forwarded around.

  • Priya Raman Turn on Deployment Protection → Preview in project settings. Visitors then need to sign in with a team account, or use a shareable link you…
  • Lena Kowalczyk Perfect — the shareable link is exactly what we need for clients.

I added shop.example-store.com to my project two days ago. The dashboard still says Invalid Configuration. My DNS has a CNAME pointing to cname.driftline-dns.net. dig shows it resolving correctly from my machine. Is there something else I need to do?

  • Priya Raman Yes — add 0 issue "letsencrypt.org" alongside the existing one. Once it propagates the check re-runs on its own within about ten minutes.
  • Jonah Pike 4471 Green now. I would never have found that, thanks.

I have this rewrite in driftline.json: { "rewrites": [{ "source": "/api/:path*", "destination": "https://api.example-shop.dev/:path*" }] } Any request to /api/products now returns 508 Loop Detected. The external API is also hosted on Driftline, in a different team.

  • kwame.dev Is the external API project also rewriting /api/* somewhere? Two projects rewriting into each other is the classic way to get a 508.
  • marcobuilds Checking — the API project has a catch-all rewrite to its own /api/index. Could that count?

process.env.FEATURE_FLAGS_URL is defined in my API routes on preview deployments but is undefined in middleware.ts. Production is fine. The variable is set for Preview and Production in project settings.

  • Theo Lindqvist Middleware runs at the edge, and edge code only sees variables that existed when it was built. If you added the variable after the last pre…
  • Lena Kowalczyk Redeployed and it is there. Might be worth a hint in the dashboard when an edge bundle predates a variable change.

After adding Prisma to a Next.js app, every deployment fails at the end of the build: Error: The Drift Function "api/orders" is 287.4 MB uncompressed, which exceeds the 250 MB limit. Locally the .next folder is small. What is pulling in so much?

  • Theo Lindqvist @kwame.dev is right. Set binaryTargets = ["native", "rhel-openssl-3.0.x"] in your schema and add the engines folder to the function exclude…
  • Ana Sofía Reyes That was it — 38 MB now and the deploy went through. Thank you both!