Dispatching (overriding) Elementary’s freshness and volume tests is limited today because some of the internal macros are called with an explicit

elementary.

prefix, which bypasses dbt’s normal dispatch mechanism. From the GitHub issue, a user tried:

yml dispatch:   - macro_namespace: elementary     search_order: ['project_x', 'elementary']

and reported that calls like

elementary.edr_cast_as_string(column)

were not dispatched to their project macro, while un-prefixed calls were. The collaborator confirmed: > we explicitly call it with the prefix

elementary.

– so the dispatch configuration is ignored and it takes the implementation from the

elementary

package. So the workaround may require patching the Elementary code and removing the prefix.[[GH issue 1540](https://github.com/elementary-data/elementary/issues/1540)] Implications for

elementary.freshness_anomalies

and `elementary.volume_anomalies`: - You can use standard dbt

dispatch

config at the package level, but any internal macro that Elementary calls with

elementary.

will not be overrideable via dispatch. - The only documented workaround is to fork/patch the Elementary package and remove those explicit

elementary.

prefixes so dbt’s dispatch can work as expected.[[GH issue 1540](https://github.com/elementary-data/elementary/issues/1540)] The knowledge sources do not provide a more targeted or official pattern for dispatching just the freshness/volume tests themselves, beyond this general limitation.