A Cell never shows real data
A query name mismatch, a resolver that returns null for a non nullable field, or an SDL that drifted from the Prisma schema, so the Empty component renders forever.
Cells resolve, UI renders
Running RedwoodJS?
Redwood is one of the more opinionated full stack React frameworks, which pays off when the conventions hold and hurts when they break. A Cell that stops resolving, an auth provider that silently returns unauthenticated, or a RedwoodSDK migration that leaves half the routes dead, all land on someone's lap with a deadline attached. We work it back to green.
What it is
RedwoodJS is a full stack React framework that bundles React on the front, GraphQL in the middle, and Prisma on the back, with generators and conventions holding the pieces together. Tom Preston-Werner and the team shipped the first public version in 2020, and the framework has since split into a classic Redwood track and the newer RedwoodSDK, which targets Cloudflare Workers.
The core ideas are Cells, which are files that declare a query and its loading and error states together, and sides, which separate API from web code at the directory level. That makes the framework feel like a well built Rails for React when the generators fit the task, and awkward when your app needs to step outside them.
The honest version
No technology is all upside. This is where RedwoodJS earns its place and where it tends to cause trouble.
Sound familiar?
The RedwoodJS problems that bring people to us, and what you have once each one is fixed.
A query name mismatch, a resolver that returns null for a non nullable field, or an SDL that drifted from the Prisma schema, so the Empty component renders forever.
Cells resolve, UI renders
A session cookie that cannot decrypt after an env var change, a dbAuth secret rotated without updating all environments, or a role check that reads the wrong claim from the token.
Users stay signed in
A service calling findUnique where find or findFirst would be correct, so a soft 404 becomes a hard Prisma exception that the frontend has no graceful path for.
Missing data handled cleanly
A large API bundle, a dependency graph that pulls everything into one chunk, or NODE_OPTIONS without enough heap set on the CI runner.
Builds complete reliably
A Worker bundle that ships too much code, unbundled dependencies, or a startup path that runs database work on the first request instead of lazily.
Cold starts inside budget
Nested relations that go past the depth limit, often from a UI that follows connections it does not actually need. The right fix is usually the query, not the limit.
Queries fit the policy
A redwood.toml with options that have been renamed or removed, or a generator that ran against a newer template than the installed framework version.
Project runs on the target version
A hotfix applied by hand to the database, a merged migration that never ran in production, or two branches that each added a migration with the same name.
Schema and migrations back in sync
What we do
Bring us a single broken Cell, or hand the whole project over for an audit.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
The Empty state renders when the query returns an empty array or null, so the first suspect is the query itself: a field that was renamed in SDL but not in the Cell, a resolver that returns null where it should return an empty list, or a Prisma relation that was never seeded. The dev tools network tab usually tells you whether the API responded with data at all; from there it is a short walk to the fix.
If your app is already in production on classic Redwood and the team is shipping fine, we rarely recommend porting just because the SDK exists. If you are starting fresh and your traffic pattern benefits from edge compute, the SDK is a reasonable pick. We look at your deploy target, your database, and your traffic shape before giving a straight answer.
Almost always a secret or environment variable mismatch. dbAuth uses an encryption key for the session cookie, and if that key differs between build time and runtime, every cookie decrypts to nothing. Auth0 and Clerk errors are usually callback URL drift or clock skew on the host. We work from the token backwards rather than guessing.
Yes, classic Redwood supports adding plain function handlers alongside GraphQL, and the RedwoodSDK track is more open to non GraphQL patterns. It works but goes against the framework's grain, and you lose Cells for those endpoints. We will tell you plainly whether the tradeoff is worth it for your case.
Usually the API bundle is pulling more dependencies than it needs, or NODE_OPTIONS on the CI runner is set too low. Raising the heap is the short term fix; trimming the API bundle, excluding server only code from the client, and splitting large services is the durable one.
Our quotes do not cost anything. Share the error output or a description of what Redwood is doing, and you get a price before a single commit lands.
Free estimate
Tell us what the CLI or the browser is saying, and a React engineer comes back with a plan and a quote.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: