I don't have the app available to me but we had a call with a customer in Snowflake hitting a nebulous error in the Publisher. I'm wondering if there's a better way to surface the actual error from the logs.
In the logs we saw things like this, which I believe are from Connect:
2026-05-20 20:11:01.553 [info] [agent] Getting R version r=/opt/R/4.5.1/bin/R
2026-05-20 20:11:01.563 [info] [agent] Parsing line for R version l=R version 4.5.1 (2025-06-13) -- \
2026-05-20 20:11:01.564 [info] [agent] Detected R version version=4.5.1
2026-05-20 20:11:01.564 [info] [agent] Detecting deployment type and entrypoint... path=/home/JGRAHN.THEKNOTWW.COM/data-science-analysis/revenue/DAREV-3924
2026-05-20 20:11:02.079 [error] [agent] Error running command command=quarto error=exit status 1
2026-05-20 20:11:02.079 [info] [agent] �[91mERROR: YAMLException: duplicated mapping key (data-science-analysis/revenue/DAREV-3924/darev-3924_attributed_bookings.qmd, 11:9)
2026-05-20 20:11:02.079 [info] [agent] 10: �[34m toc-location: left�[91m
2026-05-20 20:11:02.079 [info] [agent] 11: �[34m optional: infinite toc scrolling�[91m
2026-05-20 20:11:02.079 [info] [agent] ~~
2026-05-20 20:11:02.079 [info] [agent] 12: �[34m toc-scroll: true�[91m�[39m
However in the UI it surfaced as:
Deployment failed localId=6X20l_ZA-UthzvsO error=unexpected response from the server (500: )
This lead to kind of a lengthy back-and-forth with Support because it was believed to be an issue in their Snowflake configuration.
I don't have the app available to me but we had a call with a customer in Snowflake hitting a nebulous error in the Publisher. I'm wondering if there's a better way to surface the actual error from the logs.
In the logs we saw things like this, which I believe are from Connect:
However in the UI it surfaced as:
This lead to kind of a lengthy back-and-forth with Support because it was believed to be an issue in their Snowflake configuration.