@Jakub Bartczuk we just committed a fix for this issue - https://github.com/ploomber/ploomber/issues/878#event-7041763576 it'll be available on our next release