bruno messias

Ok, no need to create a new issue; your problem has already been described here." https://github.com/dbt-labs/dbt-core/issues/10433

Hi @CraigWilson-ZOE, this seems similar to https://github.com/dbt-labs/dbt-core/issues/10891 and #10139. This is not the raw code for the model, right? Can you share the raw code? As I discuss in https://github.com/dbt-labs/dbt-core/issues/10908...

In the meantime, testing a simpler model that uses the same macro in a non-incremental model might help. I tend to believe that your issue isn't related to the model...

I don't think there is an easy way to do that, as pointed in https://github.com/dbt-labs/dbt-core/issues/8499. The CTE approach will solve some limitations but will impact the performance , and will...

There are so many issues whose root cause is this limitation, and users are incorrectly associating it with other things. Wouldn't it be helpful to improve the unit test doc...

This will not work with the current limitations of unit tests. However, you can override the macro since it is being called only once. In that case, having a feature...