hi @Adam Bloom! that's the source of the error yep -- this has been fixed in the 1.0 release, and if you configure your dbt_cli_resource with {"json_log_format": False}, then that should work as a temporary workaround (logs in the UI won't look quite as good as before, but better than pure json)