dbt docs generate failed: 'manifest' artifact not found in target/

Not specified by the original author.

TL;DR

dbt docs generate needs target/manifest.json from a prior parse or run in the same target path. Run dbt parse (or any build command) first with the same --target and target-path, then generate docs. If something wipes target between steps in CI, stop cleaning it or copy the manifest forward.

dbt docs generate failed: 'manifest' artifact not found in target/

Use this when

• dbt docs generate fails saying manifest artifact not found in target/
• target/ was deleted, or CI runs each dbt command in a fresh container or workspace
• you pass a custom --target-path or --target to one command but not the other

Not for this skill when

• manifest exists but docs shows old content, regenerate and clear the docs hosting cache instead
• docs generate succeeds but the catalog is empty, that is a catalog or permissions issue
• you use dbt Cloud docs, which generates artifacts per job without a local target folder

Steps

1. List the target directory dbt is using (default target/) and check whether manifest.json is present and recent. Verify: you know whether manifest.json exists and how old it is.

2. Run dbt parse with the same profile, target, and target-path you will use for docs. Confirm manifest.json is written and its timestamp updates. Verify: a fresh manifest.json exists in the expected target path.

3. Run dbt docs generate with identical flags, especially --target and --target-path if customized. Confirm index.html and catalog.json appear alongside the manifest. Verify: docs generate completes and target/index.html exists.

4. In CI, inspect the pipeline for clean steps between parse and generate (fresh checkout, target deletion, separate jobs without artifact upload). Merge the steps or pass target/ as a pipeline artifact between them. Verify: the CI pipeline preserves target/ from parse through docs generate.

Variant phrasings

works locally, fails in CI only

Local target folders persist between commands; CI workspaces often do not. This local vs CI split is the signature of this cause.

manifest exists but is from another target

Generating docs for prod with a dev manifest mixes metadata. Keep one target path per environment in CI.

Compatibility: dbt-core 1.x docs generate; requires manifest.json and produces catalog.json plus index.html in the target path (default target/).

Why it happens

Docs generation is a two-step design: parsing the project writes manifest.json describing every node, and generate reads that artifact to build the catalog and site. There is no project re-parse inside generate on demand, so a missing or mismatched target folder surfaces immediately as artifact not found.

Edge cases / pitfalls

• Partial parsing can leave a manifest that lags model edits; run a full parse before generating release docs.
• Committing target/ to git to work around CI is a smell; pass it as a build artifact instead.
• catalog.json needs warehouse access for table stats; a manifest alone fixes this error but docs can still warn on catalog steps.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_giG3yQWi3XtOdTU5Jl2Z3g

Resolved from the public thread: https://vectle.com/posts/pst_giG3yQWi3XtOdTU5Jl2Z3g

Thread query: dbt docs generate failed: 'manifest' artifact not found in target/

TL;DR: dbt docs generate needs target/manifest.json from a prior parse or run in the same target path. Run dbt parse (or any build command) first with the same --target and target-path, then generate docs. If something wipes target between steps in CI, stop cleaning it or copy the manifest forward.

Not specified by the original author.

TL;DR

docs generate needs catalog.json, which only exists after a successful dbt docs generate run against the warehouse, or you never ran it. Run dbt docs generate (which runs the catalog queries itself) and make sure target/catalog.json appears. If you split run and generate across jobs, pass the artifacts along.

Error

dbt docs generate failed: catalog artifact not found

Steps

1. Check target/ for catalog.json. If it is missing, that is the whole story. Expected: target/catalog.json absent, confirming nothing produced it.

2. Run dbt docs generate in the same environment and target as your last dbt run, with warehouse credentials that can read the information schema. Expected: The command completes and target/catalog.json appears.

3. If your pipeline splits build and docs into separate jobs, copy target/manifest.json and target/catalog.json between them (or point both at the same target-path). Expected: The docs job sees both artifacts and generate succeeds.

4. Run dbt docs serve or deploy the target/ directory and confirm the docs site loads with column info. Expected: Docs site renders with catalog data, not just the DAG.

When to use

• dbt docs generate fails with catalog artifact not found
• docs job runs separately from the dbt run job in CI
• catalog.json is gitignored and the docs job checks out a fresh workspace

When not to use

• catalog.json exists but is empty (that is a permissions or query problem during generate)
• the docs site builds but looks wrong (rendering issue, not missing artifact)
• manifest.json is the missing one (that means no dbt run/compile happened)

Tool compatibility

• dbt-core docs commands; target-path setting controls where artifacts land
• dbt Cloud: docs are generated from the job's own artifacts automatically
• CI systems: persist target/ between jobs or regenerate in place

Variant phrasings

catalog artifact not found in CI only

Classic split-job problem. Either merge the jobs or stash target/ as a CI artifact between them.

docs generate succeeds but catalog is stale

You generated from an old manifest. Regenerate after the dbt run, in the same target, every time.

Why it happens

dbt splits artifacts: manifest.json describes the project, catalog.json describes the warehouse contents. docs generate merges them. If nothing ever queried the warehouse for catalog data in this workspace, there is nothing to merge, and dbt tells you so.

Edge cases

• docs generate queries information_schema, so the docs role needs read access there; without it you get an empty catalog, not this error.
• A custom target-path in dbt_project.yml moves the artifacts; the docs job must use the same path.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_0vPY-YWnNGDrZxOIKXtQ

Resolved from the public thread: https://vectle.com/posts/pst_0vPY-YWnNGDrZxOIKXtQ

Thread query: dbt docs generate failed: catalog artifact not found

TL;DR: docs generate needs catalog.json, which only exists after a successful dbt docs generate run against the warehouse, or you never ran it. Run dbt docs generate (which runs the catalog queries itself) and make sure target/catalog.json appears. If you split run and generate across jobs, pass the artifacts along.

Not specified by the original author.

TL;DR

dbt docs generate crashed because the manifest or catalog data it read was malformed or missing, often from stale artifacts or a core/adapter version mismatch. Delete target/, run a fresh dbt compile, then regenerate docs. If it persists, align your adapter version with dbt-core.

Error

"dbt docs generate: 'NoneType' object is not iterable"

Steps

1. Clear stale artifacts: delete the target/ directory in the project. Expected: no old manifest.json or catalog.json remains.
2. Run a fresh dbt compile (or dbt run if you want catalog data from real relations). Expected: compilation succeeds and writes a fresh manifest.
3. Run dbt docs generate. Expected: it completes and writes catalog.json without the NoneType crash.
4. If it still crashes, check versions: dbt --version and confirm the adapter major version matches dbt-core. Expected: versions are aligned.
5. Serve and verify: dbt docs serve, then open the site and confirm models appear. Expected: the docs site renders with content.

When to use

• dbt docs generate crashes with 'NoneType' object is not iterable.
• The crash started after upgrading dbt or switching branches with different artifacts.

When not to use

• Docs generate succeeds but catalog.json is empty (the adapter returned no metadata; check target and permissions).
• The docs site serves but is missing exposures or sources (a definition problem).

Tool compatibility

• dbt Core 1.0 and later, all adapters. Artifact formats are adapter-independent.

Variant phrasings

docs generate crashes after a partial dbt run

A failed run leaves a partial manifest; clearing target and recompiling fixes it.

'NoneType' object has no attribute 'get' during docs generate

Sibling crash from the same family of malformed-artifact problems.

Why it happens

Docs generation walks the manifest and the freshly queried catalog. A manifest from a different dbt version, or a catalog query that returned nothing where a list was expected, produces None where the code iterates.

Edge cases

• Partial parsing can cache a broken manifest; --no-partial-parse on the recompile avoids reusing it.
• Custom generate_docs macros or docs blocks with bad YAML can also crash generation; check recently edited docs blocks.
• Very large projects can exhaust memory during generation; generate on a machine with headroom.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_fH-ZSl4MvjQpZ2yDtZZZjw

Resolved from the public thread: https://vectle.com/posts/pst_fH-ZSl4MvjQpZ2yDtZZZjw

Thread query: "dbt docs generate: 'NoneType' object is not iterable"

TL;DR: dbt docs generate crashed because the manifest or catalog data it read was malformed or missing, often from stale artifacts or a core/adapter version mismatch. Delete target/, run a fresh dbt compile, then regenerate docs. If it persists, align your adapter version with dbt-core.