What this technology usually controls
React is commonly responsible for component interfaces, state, effects, routing, and client rendering. A failure may surface in the interface even when its cause sits in configuration, permissions, lifecycle, or deployment.
Common AI-generated failure patterns
Generated implementations often cover the happy path but omit version constraints, retries, authorization, durable error handling, migration safety, or production configuration. Effect loops, stale state, duplicated components, key errors, and server/client boundaries deserve explicit review.
How I diagnose it
I start with a repeatable user or request path, then follow the evidence across browser, server, provider, and data logs. The goal is to identify the contract that failed rather than replace code that merely reported the failure.
What to send
Provide the project URL, repository or builder, exact error, relevant provider event or request ID, runtime versions, and the last known-good behavior. Never send private keys through the intake form.