Build Failures

Match your build error to a fix -- config mistakes, MDX syntax errors, missing files, OpenAPI issues, and timeouts.

Open the failed build in your Deployments tab and match the error message to a section below.

Finding the Error

  1. Go to your project's Deployments tab
  2. Click the failed build
  3. Review the error message and log

The log shows exactly what went wrong and where.

Common Failures

Invalid Configuration

Error: "Invalid docs.json"

Your docs.json has syntax or schema errors.

Fix:

  1. Check for missing commas, brackets, or quotes
  2. Run jamdesk validate locally
  3. Compare against the schema reference

Missing Pages

Error: "Page 'path/to/page' not found"

A page in navigation doesn't exist.

Fix:

  • Verify the file exists
  • Check the path matches exactly (case-sensitive)
  • Don't include .mdx extension in docs.json

MDX Syntax Errors

Error: "MDX compilation failed"

Invalid MDX or JSX syntax.

Common causes:

  • Unclosed tags: <Card> without </Card>
  • Unescaped braces: { instead of \{
  • Invalid props: title=value instead of title="value"

Missing Images

Error: "Asset not found"

An image referenced in MDX doesn't exist.

Fix:

  • Check the image path is correct
  • Paths are relative to your docs directory
  • Verify the file was committed to Git

Debugging Steps

1
Read the error

The log tells you exactly what failed and where.

2
Test locally

Run jamdesk dev to reproduce the error.

3
Validate config

Run jamdesk validate to check your configuration.

4
Check recent changes

Review your last commit for the issue.

Still Stuck?

If you can't resolve the issue:

  1. Copy the full build log
  2. Note your project ID
  3. Contact support
Error Reference

All error codes explained

CLI Overview

Test builds locally