Debug errors
- 1 General process of debugging
- 2 Types of errors
- 3 Runtime Errors
- 4 Compilation Errors
- 5 Dependency Errors
- 6 Database Errors
- 7 Common pitfalls
- 8 FAQs
- 9 Common reasons
- 10 Resolution
- 11 Additional resources
General process of debugging
Learning how to debug is a skill, and one that will make you great at your role!
- Read the error message — when writing the code behind dbt, we try our best to make error messages as useful as we can. The error message dbt produces will normally contain the type of error (more on these error types below), and the file where the error occurred.
- Inspect the file that was known to cause the issue, and see if there's an immediate fix.
- Isolate the problem — for example, by running one model a time, or by undoing the code that broke things.
- Get comfortable with compiled files and the logs.
- The
target/compiled
directory containsselect
statements that you can run in any query editor. - The
target/run
directory contains the SQL dbt executes to build your models. - The
logs/dbt.log
file contains all the queries that dbt runs, and additional logging. Recent errors will be at the bottom of the file. - dbt Cloud users: Use the above, or the
Details
tab in the command output. - dbt Core users: Note that your code editor may be hiding these files from the tree viewA view (as opposed to a table) is a defined passthrough SQL query that can be run against a database (or data warehouse). VSCode help).
- The
- If you are really stuck, try asking for help. Before doing so, take the time to write your question well so that others can diagnose the problem quickly.
Types of errors
Below, we've listed some of common errors. It's useful to understand what dbt is doing behind the scenes when you execute a command like dbt run
.
Step | Description | Error type |
---|---|---|
Initialize | Check that this a dbt project, and that dbt can connect to the warehouse | Runtime Error |
Parsing | Check that the Jinja snippets in .sql files valid, and that .yml files valid. | Compilation Error |
Graph validation | Compile the dependencies into a graph. Check that it's acyclic. | Dependency Error |
SQL execution | Run the models | Database Error |
Let's dive into some of these errors and how to debug 👇. Note: not all errors are covered here!
Runtime Errors
Note: If you're using the dbt Cloud IDE to work on your project, you're unlikely to encounter these errors.
Not a dbt project
Running with dbt=0.17.1
Encountered an error:
Runtime Error
fatal: Not a dbt project (or any of the parent directories). Missing dbt_project.yml file
Debugging
- Use
pwd
to check that you're in the right directory. If not,cd
your way there! - Check that you have a file named
dbt_project.yml
in the root directory of your project. You can usels
to list files in the directory, or also open the directory in a code editor and see files in the "tree view".
Could not find profile
Running with dbt=0.17.1
Encountered an error:
Runtime Error
Could not run dbt
Could not find profile named 'jaffle_shops'
Debugging
- Check the
profile:
key in yourdbt_project.yml
. For example, this project uses thejaffle_shops
(note plural) profile:
profile: jaffle_shops # note the plural
- Check the profiles you have in your
profiles.yml
file. For example, this profile is namedjaffle_shop
(note singular).
jaffle_shop: # this does not match the profile: key
target: dev
outputs:
dev:
type: postgres
schema: dbt_alice
... # other connection details
- Update these so that they match.
- If you can't find your
profiles.yml
file, rundbt debug --config-dir
for help:
$ dbt debug --config-dir
Running with dbt=0.17.1
To view your profiles.yml file, run:
open /Users/alice/.dbt
- Then execute
open /Users/alice/.dbt
(adjusting accordingly), and check that you have aprofiles.yml
file. If you do not have one, set one up using these docs
Failed to connect
Encountered an error:
Runtime Error
Database error while listing schemas in database "analytics"
Database Error
250001 (08001): Failed to connect to DB: your_db.snowflakecomputing.com:443. Incorrect username or password was specified.
Debugging
- Open your
profiles.yml
file (if you're unsure where this is, rundbt debug --config-dir
) - Confirm that your credentials are correct — you may need to work with a DBA to confirm this.
- After updating the credentials, run
dbt debug
to check you can connect
$ dbt debug
Running with dbt=0.17.1
Using profiles.yml file at /Users/alice/.dbt/profiles.yml
Using dbt_project.yml file at /Users/alice/jaffle-shop-dbt/dbt_project.yml
Configuration:
profiles.yml file [OK found and valid]
dbt_project.yml file [OK found and valid]
Required dependencies:
- git [OK found]
Connection:
...
Connection test: OK connection ok
Invalid dbt_project.yml
file
Encountered an error while reading the project:
ERROR: Runtime Error
at path []: Additional properties are not allowed ('hello' was unexpected)
Error encountered in /Users/alice/jaffle-shop-dbt/dbt_project.yml
Encountered an error:
Runtime Error
Could not run dbt
Debugging
- Open your
dbt_project.yml
file. - Find the offending key (e.g.
hello
, as per "'hello' was unexpected")
name: jaffle_shop
hello: world # this is not allowed
- Use the reference section for
dbt_project.yml
files to correct this issue. - If you're using a key that is valid according to the documentation, check that you're using the latest version of dbt with
dbt --version
.
Compilation Errors
Note: if you're using the dbt Cloud IDE to work on your dbt project, this error often shows as a red bar in your command prompt as you work on your dbt project. For dbt Core users, these won't get picked up until you run dbt run
or dbt compile
.
Invalid ref
function
$ dbt run -s customers
Running with dbt=0.17.1
Encountered an error:
Compilation Error in model customers (models/customers.sql)
Model 'model.jaffle_shop.customers' (models/customers.sql) depends on a node named 'stg_customer' which was not found
Debugging
- Open the
models/customers.sql
file. cmd + f
(or equivalent) forstg_customer
. There must be a file namedstg_customer.sql
for this to work.- Replace this reference with a reference to another model (i.e. the filename for another model), in this case
stg_customers
. OR rename your model tostg_customer
Invalid Jinja
$ dbt run
Running with dbt=0.17.1
Compilation Error in macro (macros/cents_to_dollars.sql)
Reached EOF without finding a close tag for macro (searched from line 1)
Debugging
Here, we rely on the Jinja library to pass back an error, and then just pass it on to you.
This particular example is for a forgotten {% endmacro %}
tag, but you can also get errors like this for:
- Forgetting a closing
}
- Closing a
for
loop before closing anif
statement
To fix this:
- Navigate to the offending file (e.g.
macros/cents_to_dollars.sql
) as listed in the error message - Use the error message to find your mistake
To prevent this:
- (dbt Core users only) Use snippets to auto-complete pieces of Jinja (atom-dbt package, vscode-dbt extestion)
Invalid YAML
dbt wasn't able to turn your YAML into a valid dictionary.
$ dbt run
Running with dbt=0.17.1
Encountered an error:
Compilation Error
Error reading jaffle_shop: schema.yml - Runtime Error
Syntax error near line 5
------------------------------
2 |
3 | models:
4 | - name: customers
5 | columns:
6 | - name: customer_id
7 | tests:
8 | - unique
Raw Error:
------------------------------
mapping values are not allowed in this context
in "<unicode string>", line 5, column 12
Debugging
Usually, it's to do with indentation — here's the offending YAML that caused this error:
version: 2
models:
- name: customers
columns: # this is indented too far!
- name: customer_id
tests:
- unique
- not_null
To fix this:
- Open the offending file (e.g.
schema.yml
) - Check the line in the error message (e.g.
line 5
) - Find the mistake and fix it
To prevent this:
- (dbt Core users) Turn on indentation guides in your code editor to help you inspect your files
- Use a YAML validator (example) to debug any issues
Incorrect YAML spec
Slightly different error — the YAML structure is right (i.e. the YAML parser can turn this into a python dictionary), but there's a key that dbt doesn't recognize.
$ dbt run
Running with dbt=0.17.1
Encountered an error:
Compilation Error
Invalid models config given in models/schema.yml @ models: {'name': 'customers', 'hello': 'world', 'columns': [{'name': 'customer_id', 'tests': ['unique', 'not_null']}], 'original_file_path': 'models/schema.yml', 'yaml_key': 'models', 'package_name': 'jaffle_shop'} - at path []: Additional properties are not allowed ('hello' was unexpected)
Debugging
- Open the file (e.g.
models/schema.yml
) as per the error message - Search for the offending key (e.g.
hello
, as per "'hello' was unexpected") - Fix it. Use the model properties docs to find valid keys
- If you are using a valid key, check that you're using the latest version of dbt with
dbt --version
Dependency Errors
$ dbt run
Running with dbt=0.17.1-rc
Encountered an error:
Found a cycle: model.jaffle_shop.customers --> model.jaffle_shop.stg_customers --> model.jaffle_shop.customers
Your dbt DAG is not acyclic, and needs to be fixed!
- Update the
ref
functions to break the cycle. - If you need to reference the current model, use the
{{ this }}
variable instead.
Database Errors
The thorniest errors of all! These errors come from your data warehouseA data warehouse is a data management system used for data storage and computing that allows for analytics activities such as transforming and sharing data., and dbt passes the message on. You may need to use your warehouse docs (i.e. the Snowflake docs, or BigQuery docs) to debug these.
$ dbt run
...
Completed with 1 error and 0 warnings:
Database Error in model customers (models/customers.sql)
001003 (42000): SQL compilation error:
syntax error line 14 at position 4 unexpected 'from'.
compiled SQL at target/run/jaffle_shop/models/customers.sql
90% of the time, there's a mistake in the SQL of your model. To fix this:
- Open the offending file:
- dbt Cloud: Open the model (in this case
models/customers.sql
as per the error message) - dbt Core: Open the model as above. Also open the compiled SQL (in this case
target/run/jaffle_shop/models/customers.sql
as per the error message) — it can be useful to show these side-by-side in your code editor.
- dbt Cloud: Open the model (in this case
- Try to re-execute the SQL to isolate the error:
- dbt Cloud: Use the
Preview
button from the model file - dbt Core: Copy and paste the compiled query into a query runner (e.g. the Snowflake UI, or a desktop app like DataGrip / TablePlus) and execute it
- dbt Cloud: Use the
- Fix the mistake.
- Rerun the failed model.
In some cases, these errors might occur as a result of queries that dbt runs "behind-the-scenes". These include:
- Introspective queries to list objects in your database
- Queries to
create
schemas pre-hooks
s,post-hooks
,on-run-end
hooks andon-run-start
hooks- For incremental models, and snapshots: merge, update and insert statements
In these cases, you should check out the logs — this contains all the queries dbt has run.
- dbt Cloud: Use the
Details
in the command output to see logs, or check thelogs/dbt.log
file - dbt Core: Open the
logs/dbt.log
file.
If you're hitting a strange Database Error
, it can be a good idea to clean out your logs by opening the file, and deleting the contents. Then, re-execute dbt run
for just the problematic model. The logs will just have the output you're looking for.
Common pitfalls
Preview
vs. dbt run
(dbt Cloud IDE users only)
There's two interfaces that look similar:
- The
Preview
button executes whatever SQL statement is in the active tab. It is the equivalent of grabbing the compiledselect
statement from thetarget/compiled
directory and running it in a query editor to see the results. - The
dbt run
command builds relations in your database
Using the Preview
button is useful when developing models and you want to visually inspect the results of a query. However, you'll need to make sure you have executed dbt run
for any upstream models — otherwise dbt will try to select from
tables and views that haven't been built.
Forgetting to save files before running
We’ve all been there. dbt uses the last-saved version of a file when you execute a command. In most code editors, and in the dbt Cloud IDE, a dot next to a filename indicates that a file has unsaved changes. Make sure you hit cmd + s
(or equivalent) before running any dbt commands — over time it becomes muscle memory.
Editing compiled files
(More likely for dbt Core users)
If you just opened a SQL file in the target/
directory to help debug an issue, it's not uncommon to accidentally edit that file! To avoid this, try changing your code editor settings to grey out any files in the target/
directory — the visual cue will help avoid the issue.
FAQs
Here are some useful FAQs to help you debug your dbt project:
-
How to generate HAR files
HTTP Archive (HAR) files are used to gather data from users’ browser, which dbt Support uses to troubleshoot network or resource issues. This information includes detailed timing information about the requests made between the browser and the server.
The following sections describe how to generate HAR files using common browsers such as Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge.
infoRemove or hide any confidential or personally identifying information before you send the HAR file to dbt Labs. You can edit the file using a text editor.
Google Chrome
- Open Google Chrome.
- Click on View --> Developer Tools.
- Select the Network tab.
- Ensure that Google Chrome is recording. A red button (🔴) indicates that a recording is already in progress. Otherwise, click Record network log.
- Select Preserve Log.
- Clear any existing logs by clicking Clear network log (🚫).
- Go to the page where the issue occurred and reproduce the issue.
- Click Export HAR (the down arrow icon) to export the file as HAR. The icon is located on the same row as the Clear network log button.
- Save the HAR file.
- Upload the HAR file to the dbt Support ticket thread.
Mozilla Firefox
- Open Firefox.
- Click the application menu and then More tools --> Web Developer Tools.
- In the developer tools docked tab, select Network.
- Go to the page where the issue occurred and reproduce the issue. The page automatically starts recording as you navigate.
- When you're finished, click Pause/Resume recording network log.
- Right-click anywhere in the File column and select Save All as HAR.
- Save the HAR file.
- Upload the HAR file to the dbt Support ticket thread.
Apple Safari
- Open Safari.
- In case the Develop menu doesn't appear in the menu bar, go to Safari and then Settings.
- Click Advanced.
- Select the Show features for web developers checkbox.
- From the Develop menu, select Show Web Inspector.
- Click the Network tab.
- Go to the page where the issue occurred and reproduce the issue.
- When you're finished, click Export.
- Save the file.
- Upload the HAR file to the dbt Support ticket thread.
Microsoft Edge
- Open Microsoft Edge.
- Click the Settings and more menu (...) to the right of the toolbar and then select More tools --> Developer tools.
- Click Network.
- Ensure that Microsoft Edge is recording. A red button (🔴) indicates that a recording is already in progress. Otherwise, click Record network log.
- Go to the page where the issue occurred and reproduce the issue.
- When you're finished, click Stop recording network log.
- Click Export HAR (the down arrow icon) or press Ctrl + S to export the file as HAR.
- Save the HAR file.
- Upload the HAR file to the dbt Support ticket thread.
Additional resources
Check out the How to generate a HAR file in Chrome video for a visual guide on how to generate HAR files in Chrome.
-
Receiving an `authentication has expired` error when trying to run queries in the IDE.
If you see a
authentication has expired
error when you try to run queries in the dbt CLoud IDE, this means your OAuth connection between Snowflake and dbt Cloud has expired.To fix this, you must reconnect the two tools.
Your Snowflake administrator can configure the refresh tokens' validity, which has a maximum 90-day validity period.
To resolve the issue, complete the following steps:
- Go to your Profile settings page, accessible from the navigation menu.
- Navigate to Credentials and click on the project you're experiencing the issue with.
- Under Development credentials, click the Reconnect Snowflake Account (green) button. This steps you through reauthentication using the SSO workflow.
If you've tried these step and are still getting this error, please contact the Support team at support@getdbt.com for further assistance.
-
Receiving a 'Could not parse dbt_project.yml' error in dbt Cloud job
The error message
Could not parse dbt_project.yml: while scanning for...
in your dbt Cloud job run or development usually occurs for several reasons:- There's a parsing failure in a YAML file (such as a tab indentation or Unicode characters).
- Your
dbt_project.yml
file has missing fields or incorrect formatting. - Your
dbt_project.yml
file doesn't exist in your dbt project repository.
To resolve this issue, consider the following:
- Use an online YAML parser or validator to check for any parsing errors in your YAML file. Some known parsing errors include missing fields, incorrect formatting, or tab indentation.
- Or ensure your
dbt_project.yml
file exists.
Once you've identified the issue, you can fix the error and rerun your dbt Cloud job.
-
How can I fix my .gitignore file?
A
.gitignore
file specifies which files git should intentionally ignore or 'untrack'. dbt Cloud indicates untracked files in the project file explorer pane by putting the file or folder name in italics.If you encounter issues like problems reverting changes, checking out or creating a new branch, or not being prompted to open a pull request after a commit in the dbt Cloud IDE — this usually indicates a problem with the .gitignore file. The file may be missing or lacks the required entries for dbt Cloud to work correctly.
Fix in the dbt Cloud IDE
To resolve issues with your
gitignore
file, adding the correct entries won't automatically remove (or 'untrack') files or folders that have already been tracked by git. The updatedgitignore
will only prevent new files or folders from being tracked. So you'll need to first fix thegitignore
file, then perform some additional git operations to untrack any incorrect files or folders.- Launch the Cloud IDE into the project that is being fixed, by selecting Develop on the menu bar.
- In your File Explorer, check to see if a
.gitignore
file exists at the root of your dbt project folder. If it doesn't exist, create a new file. - Open the new or existing
gitignore
file, and add the following:
# ✅ Correct
target/
dbt_packages/
logs/
# legacy -- renamed to dbt_packages in dbt v1
dbt_modules/- Note — You can place these lines anywhere in the file, as long as they're on separate lines. The lines shown are wildcards that will include all nested files and folders. Avoid adding a trailing
'*'
to the lines, such astarget/*
.
For more info on
gitignore
syntax, refer to the Git docs.- Save the changes but don't commit.
- Restart the IDE by clicking on the three dots next to the IDE Status button on the lower right corner of the IDE screen and select Restart IDE.
-
Once the IDE restarts, go to the File Explorer to delete the following files or folders (if they exist). No data will be lost:
target
,dbt_modules
,dbt_packages
,logs
-
Save and then Commit and sync the changes.
-
Restart the IDE again using the same procedure as step 5.
-
Once the IDE restarts, use the Create a pull request (PR) button under the Version Control menu to start the process of integrating the changes.
-
When the git provider's website opens to a page with the new PR, follow the necessary steps to complete and merge the PR into the main branch of that repository.
- Note — The 'main' branch might also be called 'master', 'dev', 'qa', 'prod', or something else depending on the organizational naming conventions. The goal is to merge these changes into the root branch that all other development branches are created from.
-
Return to the dbt Cloud IDE and use the Change Branch button, to switch to the main branch of the project.
-
Once the branch has changed, click the Pull from remote button to pull in all the changes.
-
Verify the changes by making sure the files/folders in the
.gitignore
file are in italics.
A dbt project on the main branch that has properly configured gitignore folders (highlighted in italics).Fix in the git provider
Sometimes it's necessary to use the git providers web interface to fix a broken
.gitignore
file. Although the specific steps may vary across providers, the general process remains the same.There are two options for this approach: editing the main branch directly if allowed, or creating a pull request to implement the changes if required:
- Edit in main branch
- Unable to edit main branch
When permissions allow it, it's possible to edit the
.gitignore
directly on the main branch of your repo. Here are the following steps:- Go to your repository's web interface.
- Switch to the main branch and the root directory of your dbt project.
- Find the
.gitignore
file. Create a blank one if it doesn't exist. - Edit the file in the web interface, adding the following entries:
target/
dbt_packages/
logs/
# legacy -- renamed to dbt_packages in dbt v1
dbt_modules/- Commit (save) the file.
- Delete the following folders from the dbt project root, if they exist. No data or code will be lost:
target
,dbt_modules
,dbt_packages
,logs
- Commit (save) the deletions to the main branch.
- Switch to the dbt Cloud IDE, and open the project that you're fixing.
- Reclone your repo in the IDE by clicking on the three dots next to the IDE Status button on the lower right corner of the IDE screen, then select Reclone Repo.
- Note — Any saved but uncommitted changes will be lost, so make sure you copy any modified code that you want to keep in a temporary location outside of dbt Cloud.
- Once you reclone the repo, open the
.gitignore
file in the branch you're working in. If the new changes aren't included, you'll need to merge the latest commits from the main branch into your working branch. - Go to the File Explorer to verify the
.gitignore
file contains the correct entries and make sure the untracked files/folders in the .gitignore file are in italics. - Great job 🎉! You've configured the
.gitignore
correctly and can continue with your development!
If you can't edit the
.gitignore
directly on the main branch of your repo, follow these steps:- Go to your repository's web interface.
- Switch to an existing development branch, or create a new branch just for these changes (This is often faster and cleaner).
- Find the
.gitignore
file. Create a blank one if it doesn't exist. - Edit the file in the web interface, adding the following entries:
target/
dbt_packages/
logs/
# legacy -- renamed to dbt_packages in dbt v1
dbt_modules/- Commit (save) the file.
- Delete the following folders from the dbt project root, if they exist. No data or code will be lost:
target
,dbt_modules
,dbt_packages
,logs
- Commit (save) the deleted folders.
- Open a merge request using the git provider web interface. The merge request should attempt to merge the changes into the 'main' branch that all development branches are created from.
- Follow the necessary procedures to get the branch approved and merged into the 'main' branch. You can delete the branch after the merge is complete.
- Once the merge is complete, go back to the dbt Cloud IDE, and open the project that you're fixing.
- Reclone your repo in the IDE by clicking on the three dots next to the IDE Status button on the lower right corner of the IDE screen, then select Reclone Repo.
- Note — Any saved but uncommitted changes will be lost, so make sure you copy any modified code that you want to keep in a temporary location outside of dbt Cloud.
- Once you reclone the repo, open the
.gitignore
file in the branch you're working in. If the new changes aren't included, you'll need to merge the latest commits from the main branch into your working branch. - Go to the File Explorer to verify the
.gitignore
file contains the correct entries and make sure the untracked files/folders in the .gitignore file are in italics. - Great job 🎉! You've configured the
.gitignore
correctly and can continue with your development!
For more info, refer to this detailed video for additional guidance.
-
I'm receiving a 'This run exceeded your account's run memory limits' error in my failed job
If you're receiving a
This run exceeded your account's run memory limits
error in your failed job, it means that the job exceeded the memory limits set for your account. All dbt Cloud accounts have a pod memory of 600Mib and memory limits are on a per run basis. They're typically influenced by the amount of result data that dbt has to ingest and process, which is small but can become bloated unexpectedly by project design choices.Common reasons
Some common reasons for higher memory usage are:
- dbt run/build: Macros that capture large result sets from run query may not all be necessary and may be memory inefficient.
- dbt docs generate: Source or model schemas with large numbers of tables (even if those tables aren't all used by dbt) cause the ingest of very large results for catalog queries.
Resolution
There are various reasons why you could be experiencing this error but they are mostly the outcome of retrieving too much data back into dbt. For example, using the
run_query()
operations or similar macros, or even using database/schemas that have a lot of other non-dbt related tables/views. Try to reduce the amount of data / number of rows retrieved back into dbt by refactoring the SQL in yourrun_query()
operation usinggroup
,where
, orlimit
clauses. Additionally, you can also use a database/schema with fewer non-dbt related tables/views.Video exampleAs an additional resource, check out this example video, which demonstrates how to refactor the sample code by reducing the number of rows returned.
If you've tried the earlier suggestions and are still experiencing failed job runs with this error about hitting the memory limits of your account, please reach out to support. We're happy to help!
-
Why am I receiving a Runtime Error in my packages?
If you're receiving the runtime error below in your packages.yml folder, it may be due to an old version of your dbt_utils package that isn't compatible with your current dbt Cloud version.
Running with dbt=xxx
Runtime Error
Failed to read package: Runtime Error
Invalid config version: 1, expected 2
Error encountered in dbt_utils/dbt_project.ymlTry updating the old version of the dbt_utils package in your packages.yml to the latest version found in the dbt hub:
packages:
- package: dbt-labs/dbt_utils
version: xxxIf you've tried the workaround above and are still experiencing this behavior - reach out to the Support team at support@getdbt.com and we'll be happy to help!
-
[Error] Could not find my_project package
If a package name is included in the
search_order
of a project-leveldispatch
config, dbt expects that package to contain macros which are viable candidates for dispatching. If an included package does not contain any macros, dbt will raise an error like:Compilation Error
In dispatch: Could not find package 'my_project'This does not mean the package or root project is missing—it means that any macros from it are missing, and so it is missing from the search spaces available to
dispatch
.If you've tried the step above and are still experiencing this behavior - reach out to the Support team at support@getdbt.com and we'll be happy to help!
-
What happens if the SQL in my query is bad or I get a database error?
If there's a mistake in your SQL, dbt will return the error that your database returns.
$ dbt run --select customers
Running with dbt=0.15.0
Found 3 models, 9 tests, 0 snapshots, 0 analyses, 133 macros, 0 operations, 0 seed files, 0 sources
14:04:12 | Concurrency: 1 threads (target='dev')
14:04:12 |
14:04:12 | 1 of 1 START view model dbt_alice.customers.......................... [RUN]
14:04:13 | 1 of 1 ERROR creating view model dbt_alice.customers................. [ERROR in 0.81s]
14:04:13 |
14:04:13 | Finished running 1 view model in 1.68s.
Completed with 1 error and 0 warnings:
Database Error in model customers (models/customers.sql)
Syntax error: Expected ")" but got identifier `your-info-12345` at [13:15]
compiled SQL at target/run/jaffle_shop/customers.sql
Done. PASS=0 WARN=0 ERROR=1 SKIP=0 TOTAL=1Any models downstream of this model will also be skipped. Use the error message and the compiled SQL to debug any errors.