Hey team! We downgraded the elementary version to 0.13.2 due to this bug. However, with this downgrade, we face a very serious problem. The on-run end-hook takes too long time to finish. As a result, the average execution time of our flows has been increased. Does anyone from the team face the same problem? Is it a known issue?

Hi @panapost, added more context and a workaround in the github issue

oh nice.. is it possible to have affect other queries this change, or will it better to find a stable solution?

if you are referring to the workaround, it might cause issues in other queries (tho not likely), i recommend playing around with the

dbt_artifacts_chunk_size

parameters if it causes issues

this workaround will solve also the problem with the increased execution time or are they different issues? I am asking because in the last 2 weeks, we have allocated too much time in order to upgrade/downgrade the package and we still facing performance issues.

Oh, regarding the on-run-end, this is a separate issue that would not be resolve by the workaround, but might be by upgrading to the latest package version. If it does not, Please open a different thread that details the issue exactly (what are you running, where, how long does it take, etc). its easier for us to handle different issues in different threads 🙏

i will open it soon, thank you once again

Hi @panapost, we are not working on it currently, but will get to it (i dont have an exact date)