The error

ValueError: 'partial success' is not a valid Status

occurs because Elementary expects only certain status values (like

error

,

fail

,

skipped

, or

warn

) in its internal status enum. If dbt or your data warehouse introduces a new status (such as

partial success

from microbatch strategies), Elementary's code may not recognize it, leading to this error. A similar issue was previously reported when BigQuery returned a status of

runtime error

, which was not recognized by Elementary and caused a

ValueError

. The resolution was to update Elementary to a version where the status enum was expanded or made more robust to handle new/unexpected statuses. The fix was released in version

0.10.0

for the

runtime error

case, and users were advised to upgrade to the latest version to resolve the issue. The relevant discussion and fix can be found [here](https://slack.com/archives/C02CTC89LAX/p1691698942521889). How to resolve: 1. Upgrade Elementary: First, upgrade to the latest version of Elementary, as these types of issues are typically addressed in newer releases when new dbt or warehouse statuses are introduced. 2. Check for Open Issues: If the problem persists after upgrading, check the [Elementary GitHub issues](https://github.com/elementary-data/elementary/issues) to see if this specific status (

partial success

) has been reported and if a fix is pending or available. 3. Temporary Workaround: If you cannot upgrade or a fix is not yet available, you may need to manually patch the status enum in your local Elementary installation to include

partial success

, similar to how the

runtime error

status was handled previously. If you are still experiencing the issue after upgrading, please provide more details or open a new issue with the Elementary team so they can address support for the

partial success

status in a future release. Summary: Upgrade Elementary to the latest version, as this is the standard resolution for unrecognized status errors. If the issue persists, report it to the Elementary team so they can add support for the new status value, just as they did for

runtime error

previously [see discussion and fix](https://slack.com/archives/C02CTC89LAX/p1691698942521889).