If events are missing dvce_created_tstamp those events will be missing in base tables

[stevensnicholas]

There is the use of dvce_created_tstamp is in a predicate in the macro

dbt-snowplow-utils/macros/base/base_create_snowplow_sessions_lifecycle_manifest.sql

Line 65 in 19d16b3

dvce_sent_tstamp <= {{ snowplow_utils.timestamp_add('day', days_late_allowed, 'dvce_created_tstamp') }} -- don't process data that's too late

. If events are processed and contain dvce_created_tstamp they will be missing

[miike]

@stevensnicholas Could you clarify what you mean by this?

If events are processed and contain dvce_created_tstamp they will be missing

This logic looks like as long as the dvce_created_tstamp is within the days_late_allowed threshold (when compared to dvce_sent_tstamp) it should be included in the model.

[stevensnicholas]

Sorry, that was a poorly worded title - if either dvce_created_tstamp or dvce_sent_tstamp are null those rows will be missing from events this run. Because either side of that where clause will be comparing to null.

[miike]

Thanks - that makes sense let me raise with the team.

[miike]

Linking #176 as an update courtesy of the brilliant @agnessnowplow

[agnessnowplow]

Closing as this should now be solved with the latest release.