Troubleshooting dbt Core collector issues
Collector runtime and troubleshooting
The catalog collector may run in several seconds to many minutes depending on the size and complexity of the system being crawled.
If the catalog collector runs without issues, you should see no output on the terminal, but a new file that matching *.dwec.ttl should be in the directory you specified for the output.
If there was an issue connecting or running the catalog collector, there will be either a stack trace or a *.log file. Both of those can be sent to support to investigate if the errors are not clear.
A list of common issues and problems encountered when running the collectors is available here.
Issue: dbt resources are not displayed after running the collector
After the collector has run successfully, the dbt resources are not displayed in data.world. Open the dbt catalog.json file to check if the file has node objects in the nodes property. If the nodes property is empty, it is most likely a permissions issue.
Cause: The account used to run the dbt docs generate command may not have sufficient permissions to query the metadata from the target database. When the account does not have sufficient permissions, you will see not see the node objects in the nodes property in the catalog.json file.
Solution: : In dbt, ensure that the account associated with running the dbt docs generate command has the correct permissions to query the metadata in the target database.