I just upgraded to v1.1.9 as well and the behaviour is still the same

@owen - mind taking a look at this error during freshness-based reconciliation? Is the issue that we don't handle source assets yet?

ah I think we might not handle the case where a source is referenced, but there's no corresponding

SourceAsset

-- should be an easy fix, thanks for the report!

I just tried the latest version and it worked as expected. Thanks!