The artifact pipeline is driven by a query against the events table that excludes rows that have already been processed.
The original version of the query had a limit clause in the nested NOT IN sub-select which was artificially excluding rows and causing events to be processed multiple times for some delivery ids.
The artifact pipeline is driven by a query against the events table that excludes rows that have already been processed.
The original version of the query had a limit clause in the nested
NOT INsub-select which was artificially excluding rows and causing events to be processed multiple times for some delivery ids.