Skip to main content
Builds fail when:
  • TypeScript type-checking fails.
  • A required env var is missing.
  • A Convex schema migration conflicts.
vly auto-retries failed builds up to 3 times (the agent self-corrects). If it still fails after 3 retries, you’ll see the build error in the deploy log.

​
Common causes

Look for “process.env.X is undefined” in the build log. Set the env var in the appropriate environment.
A schema field changed type but a query still references the old type. Re-prompt to fix, or hand-edit the query.
Often after renaming a file. Cmd+Shift+F to find broken imports; fix the path.
Two branches changed the same field. Resolve by picking one; re-prompt the conflicting branch with the resolution.

​
Reading the build log

In vly’s editor → Deploys → click the failed build. The log shows:
  1. Build start time.
  2. Type-check pass (or fail with specific errors).
  3. Bundle pass.
  4. Deploy pass.
The error usually has a file:line indicator pointing at the problem.

​
Fixing

The fastest fix path:
1

Read the error message

Most errors are clear once read carefully.
2

Re-prompt to fix

“Fix the TypeScript error on line 42 of components/TaskRow.tsx.” The agent reads the error and applies the right fix.
3

Or hand-edit in Code mode

For one-line fixes, manual is fastest.
4

If the schema is the issue

Check convex/schema.ts and the affected query for type alignment.

Common errors

Specific patterns.

Convex migrations

Schema evolution.

Debugging workflow

Systematic approach.
Last modified on April 18, 2026