Troubleshooting dbt cloud 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 1: Collector fails to complete because it cannot find catalog.json
Errors observed: The following error message is observed in the log files:
A server error occurred, retrying. Server response: InboundJaxrsResponse{context=ClientResponse{method=GET, uri=https://cloud.getdbt.com/api/v2/accounts/X/runs/X/artifacts/catalog.json, status=502, reason=Bad Gateway}}
Cause: The catalog.json is a required file and was not generated for a job.
Solution: Review and ensure that the Job Execution settings are configured properly.
Issue 2: The collector runs but no dbt resources are found in the collector output file
Error observed: The following error message is observed in the log files:
No successful run with artifacts found for the specified filters.
Cause: The Job execution setting is not configured and as a result the collector is not able to harvest the dbt resources.
Solution: Review and ensure that the Job Execution settings are configured properly.