# DBT Cloud Explore shows Missing Table Metadata, despite successful docs generate job run

**URL:** <https://discourse.getdbt.com/t/dbt-cloud-explore-shows-missing-table-metadata-despite-successful-docs-generate-job-run/16867>\
**Category:** Help\
**Tags:** dbt-cloud\
**Created:** [November 6, 2024, 11:31am UTC](https://discourse.getdbt.com/t/dbt-cloud-explore-shows-missing-table-metadata-despite-successful-docs-generate-job-run/16867 "2024-11-06T11:31:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![richkirk922](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/richkirk922/32/4781_2.png) [@richkirk922](https://discourse.getdbt.com/u/richkirk922)\
**Post date:** [November 6, 2024, 11:31am UTC](https://discourse.getdbt.com/t/dbt-cloud-explore-shows-missing-table-metadata-despite-successful-docs-generate-job-run/16867/1 "2024-11-06T11:31:24Z")

</div>

## The problem I’m having

dbt Cloud Explore shows Missing Table Metadata for all models, despite successful docs generate job run

## What I’ve already tried

Ensuring job has succesfully run for environment with successful docs generate run step

## Some example code or error messages

```auto
Missing Table Metadata

```

---

<div class="post-metadata">

**Author:** ![richkirk922](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/richkirk922/32/4781_2.png) [@richkirk922](https://discourse.getdbt.com/u/richkirk922)\
**Post date:** [November 6, 2024, 12:58pm UTC](https://discourse.getdbt.com/t/dbt-cloud-explore-shows-missing-table-metadata-despite-successful-docs-generate-job-run/16867/2 "2024-11-06T12:58:28Z")

</div>

Found the problem: It is the standard dbt schema prefix behavior that needs to be overridden for docs generate command, by overriding the macro generate\_schema\_name(). We were already doing this for the main run command, but needs to also be done for docs generate - so in our case added an explicit step in the job to call “dbt docs generate” adding our custom project var (that then calls the override), instead of relying on the job checkbox “Generate docs on run”