dbt Cloud Explore shows Missing Table Metadata for all models, despite successful docs generate job run
Ensuring job has succesfully run for environment with successful docs generate run step
Missing Table Metadata
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”